Re: distribution customization

[Matthew Miller <mattdm mattdm org>]

On Wed, Jan 10, 2007 at 02:26:03PM -0500, Bill Nottingham wrote:
> Potential implementations of this:
>  a) Ship a kickstart file in the spin that's used by default.
>  
>     Pros: Easily expandable to do anything we want, through the use
>           of %post
> 	  Allows for future expansion and automatic support of
> 	  any new anaconda features.
>     Cons: If we want the concept of 'setting defaults' that the
>           user of the spin can change, will need some reinterpretation
> 	  of how kickstart is used inside of anaconda. Unless I've
> 	  missed something.

I think this is nice and elegant. Jeremy was taking about this last month
<https://www.redhat.com/archives/anaconda-devel-list/2006-December/msg00043.html>.

A change then would be a way to set a value in kickstart as either a
default-just-use-this-and-don't-ask or a
default-to-show-preselected-in-the-gui.



>  a) A package containing whatever files are used to customize that
>     pungi/whatever uses when building the image.
>     Pros: Easy to drop whatever customizations onto the filesystem
>     Cons: Well, either you have packages that Aren't Fedora in the spins,
>           or you make someone go through and review them.

Someone should go through and review them anyways, shouldn't they?

-- 
Matthew Miller           mattdm mattdm org          <http://mattdm.org/>
Boston University Linux      ------>              <http://linux.bu.edu/>