On 15-Jan-08, at 9:20 PM, Shawn Walker wrote: > On Jan 15, 2008 11:10 PM, John Sonnenschein <johnsonnenschein at gmail.com > > wrote: >> forgive me if this has been discussed before, I couldn't find mention >> of it in the archives... >> >> What's the problem with having an installer option such as "advanced" >> somewhere in the user setup section that would allow a user to choose >> what the default environment will be > > This has been discussed before, at the Summit in fact. > > The short of it is that an advanced installation path quickly gets > complicated.
Hence the name. > You start with one installation option, and before you know it, you > end up with a thousand. hyperbole. last time I installed redhat they had an advanced path that wasn't bad > Dave and his team, from what I gather, are focused on a simple, great > install experience foremost. then they have failed before they started. removing all possibility for options as a design decision is failure to create a great install experience. > That is what they have the need for. > > While Dave may not be personally interested nor have the time (due to > resource allocation) to support a more "advanced installation path", > from talking with him, it is clear that they have intentionally left > "hooks" in the install code so that others can implement this > functionality if they so desire. > > Remember that caiman is just an installer, it doesn't know anything > about "GNU" or "BSD" for that matter. > > You need to talk with the distributions using the installer if you > want to influence choices they are making. > >> the only other option I can see is to fork indiana to get a legacy- >> compatible version > > Or just use the distribution constructor...not difficult. that /is/ a fork.
