Merge lp:~james-w/linaro-image-tools/architectures-from-config into lp:linaro-image-tools/11.11
Proposed by
James Westby
Status: | Merged |
---|---|
Approved by: | Michael Hudson-Doyle |
Approved revision: | 108 |
Merged at revision: | 66 |
Proposed branch: | lp:~james-w/linaro-image-tools/architectures-from-config |
Merge into: | lp:linaro-image-tools/11.11 |
Prerequisite: | lp:~james-w/linaro-image-tools/architecture-support |
Diff against target: |
178 lines (+108/-6) 2 files modified
hwpack/config.py (+47/-1) hwpack/tests/test_config.py (+61/-5) |
To merge this branch: | bzr merge lp:~james-w/linaro-image-tools/architectures-from-config |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michael Hudson-Doyle (community) | Approve | ||
Review via email: mp+34467@code.launchpad.net |
Description of the change
Hi,
Here's a small branch that adds architectures to the configuration file.
I decided that we want the configuration to at least state which
architecture(s) it is intended for. We can add ways to limit/expand this
list at build time later if we want.
Firstly this branch adds the code and tests to ensure that the architectures
list is present and has at least one entry.
Then it adds a property for getting the list of architectures.
Lastly it also adds a property to get the sources. I folded this in as it is
very small, and along the same lines. There are already tests for the validity
of the sources specification.
Thanks,
James
To post a comment you must log in.
It all looks fine.
I'm not sure of the motivation for filtering out duplicates in the accessor methods -- wouldn't complaining during validation make just as much sense?