Kyle McDonald wrote: > I don't understand the suggestion to 'avoid the conflicts'... How can I > avoid having the Solaris Perl or GDB or whatever tool not conflict with > the one I'm installing for my users?
It sounds like you really want to be able to choose to NOT install some set of Sun provided OSS packages, because you wish to provide them for yourself, and you are willing/able to cause your user(s) to modify their PATH to include the install location for your new programs. The problem you have identified is the creeping dependencies that get stuck on the Sun provided packages - you can't "not install" Sun's Perl and install your own because something else in Solaris depends on the "Sun Perl". If you *were* able to do the above (as an admin), would you still have the same issues with this proposal? -John
