Hi Karen,
On Wed, 29 Sep 2010, Karen Tung wrote:
I don't like option (a) because of problems others already mentioned.
I don't like option (b) because we are including software related
information
in the <distro_spec> section of the manifest.
What about option (c).
Add something in the "software section" since this is kind of related to
software.
<software name="ba-arch">
<software_data action="do-not-compress" type="FILE">
<name>file1</name>
<name>file2</name>
....
This way, it will be easy to read, even for long list of files. The
manifest
parser already take care of parsing and putting this kind of input in the
DOC.
The ba-arch checkpoint can get the list easily.
This way it's readable.
But, two things:
a) I don't know if it's stretching the software section beyond
what it was defined for -- which was, the payload for an
install/uninstall in most cases.
b) This is going to require a change to the schema albiet a small
one. If we were to stop using dcfs down the line, then the
schema would have to change once more.
Is readability really that big a deal with my proposed solution
(a) given that this file list will rarely change?
Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
