Keith Bierman <[EMAIL PROTECTED]> writes: > On Aug 6, 2007, at 4:37 PM, [EMAIL PROTECTED] wrote: > >> >> I think for the moment that Indiana should follow this precedent since >> Indiana should replace Solaris Express and eventually find its way out >> in a long-term support release such as Solaris 11^H^HNext. And while >> we definitely want to attact new users to OpenSolaris, we certainly >> want to avoid creating new issues for existing users of the >> technology. > > Since the new user is not going to put the new stuff in their path, > this ensures failure to capture. > > I have no objection to keeping things in /usr/gnu and friends ... IFF > the default PATH is hacked to have them show up first. > > Otherwise, we're putting a ton of effort into a waste of time. If all > we wanted to do is have Solaris out sooner, we have that already with > Solaris Express. >
You have the choice between alienating your existing user base, or the hypothetical new user base. I think the best course is probably to give the user a (gui-driven) choice. I also think you overstate the result of not defaulting to GNU-ish tools, but that's neither here nor there. -- Rich _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
