Hi Jean.
Your plan sounds good to me. More inline.
Jean McCormack wrote:
> I'm starting to work on modifications to the Distro Constructor to
> support generating a sparc image.
>
> Here's my plan, comments are welcome.
>
> 1) There are some changes as expected to the manifest file. These are
> changes to the package list,
> the bootroot contents files, and possibly finalizer scripts (not sure
> on that yet). I've considered
> adding parameters to each package and file to specify architecture but
> that just seems clumsy
> and there may in the future be finalizer script changes etc. So right
> now I'm going with the
> decision that there will be separate manifest files. For example:
> slim_cd_sparc.xml
>
Yes, this is the benefit and purpose of having manifest files.
Different package lists and different bootroot files and processing for
different scenarios, including different architectures.
> 2) There are some sparc specific changes to bootroot_archive and
> bootroot_initialize. These
> are not large and they fit in nicely with the structure of the code.
> For example, after cpio'ing
> the files to the bootroot they need to be fiocompressed. I can
> easily test for a sparc architecture
> and then fiocompress. As long as the changes remain in the "clean"
> and "small" range I'll
> do this. If they become larger and more code intrusive I'll
> investigate using separate finalizer scripts.
>
This strikes a good balance between the lack of maintainability
introduced by extra scripts, with the lack of clarity when introducing
architecture specific (sparc/x86) code to the scripts.
An occasional architecture-specific thing in a script won't make the
script harder to read, and will keep the number of architecture-specific
scripts down.
Thanks,
Jack
>
> Jean
>
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
