Jack Schwartz wrote: > Hi everyone. > > I have some loose ends to tie up or confirm with regards to the system > specification manifest passed to the Distro-Constructor. > > Questions: > ---------- > > 1) Not sure what extra things DC needs to do to provide for a live-image > installable image or a repo-installable image. It will need to include > an installer, but how does that fit with the manifest? >
I would think the installer is just one or more packages that are included in the image. > 2) Disk and network parameters for installation are still TBD. > > 3) There are some things which cannot be known by the DC but which are > needed by it. For example, if someone specifies they want a certain > locale, I don't want to hardwire into DC a package name delivering that > locale. For maintainability, these things will have to go into a > manifest. I'm thinking of putting them into a manifest different than > the one for user-specified parameters. That way if the supported locale > list changes, one can just upgrade their DC and get the changes without > worry of overwriting or having to merge the user's existing > user-specified parameter manifest. > I don't think that we should assume package name == locale. Files for specific locales might be tagged as such and aggregated into larger packages. But we need some feedback from g11n on what they're actually going to do. > Assumptions: > ------------ > > 1) When installing from the live image that all parameters are AS-IS > from the live image. (e.g. same users, files, locales, etc) > I suppose, though I'm wondering what effect this assumption has? > 2) A list of supported keyboard types is not included because all are > currently delivered in a single package and I assume it will stay that > way once packages are refactored (as keyboard map files are small). Yeah, I don't see why we'd split it. > This is not to be confused with locales which are included in the manifest. > > Other items: > ------------ > > 1) The manifest now specifies tags and attributes can be specified for > each package or incorporation. This is the plan for narrowing down what > gets installed. (Tags are for file types, and attributes deal with > packages.) > OK. > 2) I have added a query for the zfs compression type and level for the > live CD and installed image. > I think you mean that this is just the setting of the compression parameter, which combines the algorithm and level. Dave
