[gnu-sol-discuss] contributing pkgs

[Eric Boutilier]

luc at nwkea-mail-4.sun.com wrote:

>Hi Eric,
>
>  
>
>>I'll take a shot at offering a simplified rendition of the proposal
>>that was made for Sun's Solaris (aka Nevada, aka SunOS 5.11) of what
>>the future structure will probably be: (Note however, as Mac pointed out,
>>for now, you should install your ports in /opt/<something>/bin)
>>
>>As much as possible, the popular GNU commands and tools will be put
>>in /usr/bin. (The /usr/sfw/bin idea is now seen as a less than optimal
>>idea.). However, where there are name conflicts, put the GNU version in
>>/usr/gnu/bin/<whatever>, leaving /usr/bin/<whatever> being the traditional
>>Solaris version (for obvious reasons of backward compatibility.)
>>    
>>
>
>Well I'm not sure anymore now... I used to compile bounch of pkgs and
>KDE (couple year ago), always as a hobby.. but after checking the the
>GNU Solaris, I realize that is it own distribution and so far it has
>alll the packages I had in mind.
>
>I have a AMD-64 laptop that I was planning to use for this, but I wanted
>to keep it in sync with Nevada since it seems to be the 'main'
>distribution So what next??...
>  
>


Based on what you've said, for your situation I'd probably go with 
Nevada/JDS; and if you want KDE instead of GNOME, use the Blastwave or 
Sunfreeware.com implementation. Just my opinion.  (Best advice though is 
never make a decision like this based on just one other person's 
opinion! :-)

--Eric

P.S. Despite the "GNU Solaris" references often associated with Nexenta, 
in reality the name of the distro is definitely Nexenta, not GNU Solaris.