[indiana-discuss] Standards ? An derivative proposal.

[John Sonnenschein]

On 14-Jan-08, at 10:41 PM, Moinak Ghosh wrote:

> Anil Gulecha wrote:
>> On 1/15/08, John Sonnenschein <johnsonnenschein at gmail.com> wrote:
>>
>>> Question.
>>>
>>> I very much am not a fan of the GNUserland & bash, not least of  
>>> which because they take the concept of standards and toss them  
>>> right out the window.
>>>
>>> Part of why I came to Solaris in the first place when the OpenSol  
>>> project launched was precisely because the default userland wasn't  
>>> full of incompatible & self-inconsistent GNU tools.
>>>
>>> It seems that the default Indiana distribution wants to remove  
>>> this compelling reason to use Solaris.
>>>
>>> So, I have a question/proposal. Is anyone other than myself  
>>> interested in taking the Indiana bits that exist currently, and  
>>> rolling a distribution with far saner and less linux-y defaults ?
>>>
>>> My idea is to have whatever development needs to be done ( and it  
>>> ought not to be much )  run parallel to the indiana-proper  
>>> development, in order to have something ready on indiana's  
>>> official release date
>>>
>>>
>>
>> Hi John,
>>
>> I'm probably will sound cynical, but isn't this just changing the  
>> slim
>> installer code to not add /usr/gnu/bin to the path. Doing this should
>> take care of the non-compatibility complaints.Is there something else
>> I'm missing?
>>
>> Are you proposing a project to take care of the above installer code?
>> And wouldn't it be a better solution to start a discussion on adding
>> an option to the installer that allows the user to select his
>> favourite userland.
>>
>
>  On similar lines, how would this distro be different from Indiana  
> other than
>  not having bash as the default shell and not having /usr/gnu/bin in  
> the PATH ?
>
> Regards,
> Moinak.

Okay, slightly better enumerated
1) GNU tools which duplicate functionality of tools already included  
in O/N should be explicitly pulled in by the user with pkg framework,  
or through an installer option ( again, with defaults set to standards  
compliance/legacy mode )
2) Defaults shall be in order of those included with legacy solaris,  
then standards compliance tools ( xpg ).
3) shell shall be 100% compatible with legacy bourne shell