On Tue, Oct 11, 2011 at 2:22 AM, Tom Gall <email address hidden> wrote:
> This can be as simple as changing linaro-media-create on line 110 to
>
> 110 ROOTFS_DIR = os.path.join(TMP_DIR, 'binary/boot/filesystem.dir')
>
> However this would not be backward compat with the older rootfs
> organization from live-build.
>
> Adding a simple existence test for say binary/etc, if that fails you
> know you have the new format and to use the directory above is probably
> the way to go... I think it might also be wise to add an version file
> in the binary-tar.tar.gz.
The binary-tar.tar.gz is the output from our builds, right? If you say
that we could leave a version file in it, possibly we could even put a
metadata file there? That could just explicitly specify the
binary/boot/filesystem.dir part to be joined with TMP_DIR.
This would be in line with the hwpacks V2 work where we have made sure
that control over paths and other specifics are handed to whoever
creates the hwpack. Could this be the start of images having metadata
as well?
>
> Thoughts?
>
> --
> You received this bug notification because you are subscribed to Linaro
> Image Tools.
> https://bugs.launchpad.net/bugs/872007
>
> Title:
> l-m-c doesn't support future live-build3
>
> Status in Linaro Image Tools:
> New
>
> Bug description:
> When linaro upgrades from live-build3-a21 to live-build3-a34, the tar
> format will change. This causes an incompatibility as the binary-
> tar.tar.gz file has a different format.
>
> Specifically the root file system is now contained in
> binary/boot/filesystem.dir
>
> For the sake of trivia, the debs installed into the file system are
> located in binary/pool
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-image-tools/+bug/872007/+subscriptions
>
On Tue, Oct 11, 2011 at 2:22 AM, Tom Gall <email address hidden> wrote: join(TMP_ DIR, 'binary/ boot/filesystem .dir')
> This can be as simple as changing linaro-media-create on line 110 to
>
> 110 ROOTFS_DIR = os.path.
>
> However this would not be backward compat with the older rootfs
> organization from live-build.
>
> Adding a simple existence test for say binary/etc, if that fails you
> know you have the new format and to use the directory above is probably
> the way to go... I think it might also be wise to add an version file
> in the binary-tar.tar.gz.
The binary-tar.tar.gz is the output from our builds, right? If you say boot/filesystem .dir part to be joined with TMP_DIR.
that we could leave a version file in it, possibly we could even put a
metadata file there? That could just explicitly specify the
binary/
This would be in line with the hwpacks V2 work where we have made sure
that control over paths and other specifics are handed to whoever
creates the hwpack. Could this be the start of images having metadata
as well?
> /bugs.launchpad .net/bugs/ 872007 boot/filesystem .dir /bugs.launchpad .net/linaro- image-tools/ +bug/872007/ +subscriptions
> Thoughts?
>
> --
> You received this bug notification because you are subscribed to Linaro
> Image Tools.
> https:/
>
> Title:
> l-m-c doesn't support future live-build3
>
> Status in Linaro Image Tools:
> New
>
> Bug description:
> When linaro upgrades from live-build3-a21 to live-build3-a34, the tar
> format will change. This causes an incompatibility as the binary-
> tar.tar.gz file has a different format.
>
> Specifically the root file system is now contained in
> binary/
>
> For the sake of trivia, the debs installed into the file system are
> located in binary/pool
>
> To manage notifications about this bug go to:
> https:/
>