Merge lp:~mabac/linaro-image-tools/bug-829220 into lp:linaro-image-tools/11.11
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 422 | ||||
Proposed branch: | lp:~mabac/linaro-image-tools/bug-829220 | ||||
Merge into: | lp:linaro-image-tools/11.11 | ||||
Diff against target: |
98 lines (+50/-4) 2 files modified
linaro_image_tools/media_create/boards.py (+10/-3) linaro_image_tools/media_create/tests/test_media_create.py (+40/-1) |
||||
To merge this branch: | bzr merge lp:~mabac/linaro-image-tools/bug-829220 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Loïc Minier (community) | Approve | ||
Review via email: mp+72405@code.launchpad.net |
Description of the change
Hi,
This branch changes the format of the Snowball startfiles.cfg format a little bit.
L-m-c will now assume that the filename in the config file is an absolute path to the file on local file system. If that file does not exist, we fall back to assuming that the filename is relative to chroot/bin as is the case before this change.
This should make it backwards compatible for existing hwpacks but let anyone creating a Snowball hwpack specifiy absolute paths in case the files won't be installed to /boot on the target.
Also, if no interpretation of the path is found, we fall back to assuming that the filename is relative to /usr/lib/
Thanks,
Mattias
On Mon, Aug 22, 2011, Mattias Backman wrote:
> This branch changes the format of the Snowball startfiles.cfg format a
> little bit.
>
> L-m-c will now assume that the filname in the config file is an
> absolute path to the file on local file system. If that file does not
> exist, we fall back to assuming that the filename is relative to
> chroot/bin as is the case before this change.
So the hwpack doesn't transport the files anymore? It seems to be the
wrong thing to encourage
Perhaps we could support looking up files in the hwpack tarball, or in deb://xyz- files.deb/ boot/xyz. bin?
a .deb in the hwpack tarball even if that isn't installed; e.g.
startfiles.cfg would point at hwpack://xyz.bin or at
hwpack+
--
Loïc Minier