On Wed, Mar 30, 2011, Eric Miao wrote:
> Loic, wouldn't split the string into list be better than explicitly
> specifying the list, using python syntax. And eventually we are going to
> encode this into hwpack v2 config file, and a string would be more
> straight forward?
I don't think we want a list in hwpack; instead the hwpack will contain
a single kernel and that will be the one flavor we're expected to use;
the hwpack creation might support finding the right kernel from
multiple locations though.
I personally find it's best to use the closest Python structure for
code, so that you use a list to contain a list of things; we can
convert the string representation from the hwpack when we read/write
hwpacks. Perhaps we will infer kernel flavors from multiple hwpacks
for instance, and then build a list from that. So I wouldn't worry
too much about the way it's serialized in data files outside of
linaro-image-tools.
On Wed, Mar 30, 2011, Eric Miao wrote:
> Loic, wouldn't split the string into list be better than explicitly
> specifying the list, using python syntax. And eventually we are going to
> encode this into hwpack v2 config file, and a string would be more
> straight forward?
I don't think we want a list in hwpack; instead the hwpack will contain
a single kernel and that will be the one flavor we're expected to use;
the hwpack creation might support finding the right kernel from
multiple locations though.
I personally find it's best to use the closest Python structure for image-tools.
code, so that you use a list to contain a list of things; we can
convert the string representation from the hwpack when we read/write
hwpacks. Perhaps we will infer kernel flavors from multiple hwpacks
for instance, and then build a list from that. So I wouldn't worry
too much about the way it's serialized in data files outside of
linaro-
--
Loïc Minier