> Collasping more crud into /usr/bin means that I will no longer be able
> to have more of a Solaris "feel" rather than a GNU feel.
This is mostly true. However, it's also true to that the things we
place in /usr/bin are *only* those things that don't conflict with
Solaris. You won't suddenly see 'ls' spitting ugly colors at you, at
least not on my watch. ;-}
> This is going to
> create a horrible mess with Solaris 11 with folks doing development
> on Solaris 10 since the dependency trees will be completely different.
Sorry, I don't see that. We add new things to Solaris all the time,
and always have. Why should anyone care specifically where those
things came from, rather than what they do?
I think the "dependencies" issue is too vague to be acted on; please
provide specifics.
> Being able to select very specific "profiles" via PATHing can help
> correctly build Open Source software with minimal effort. This glomming
> of stuff into /usr/bin is going to 1) make it impossible to run a
In PSARC 2005/185, we essentially ruled that sort of separation out
because it caused more trouble than it was worth.
> Obviously, there's no sense in arguing with the Ivory Tower who can't
> understand what a completely disorganized and irresponsible response
> to a requirement for more compatiblity and feature sets this path takes
This is where I think you're actually wrong. There *is* sense in
arguing, because the wished-for Ivory Tower doesn't exist. The ARC is
composed of people -- engineers, in fact -- who donate their time to
help make decisions like this, based on input from everyone. It's an
open forum, not a tower.
> If I want Solaris, I want Solaris. If I want Solaris/Gnu, I can path it that
> way.
> The road we're heading down leaves me one of three options
> 1) run Solaris 10 into the ground
> 2) deal with Glomaris 11
> 3) start my own Open Solaris Distro. Least I have 14 years of porting
> experience
I think you missed one clear and potentially useful answer:
4) File your own ARC case that proposes overturning PSARC 2005/185,
and describe exactly how you're going to balance in a better way
all of the costs and benefits that previous case did.
I don't see how the decision we made there was actually wrong, but I
can say that I'm certainly willing to learn.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
