I'm assuming the "default link" packages would be installed by default - our marketing would demand that.
This implies to me, that all this proposal would buy you is the ability to go out of your way to construct a system where the various components could be selected by path without a fall through to /usr/bin. In a distributed computing world, you couldn't depend upon this. How many people would use this? Well, Kyle seems to be one. There are undoubtedly others, but how many? I don't think the gain is worth the effort. Your mileage may vary. - jek3 John Plocher wrote: > Kyle McDonald wrote: >> John Plocher wrote: >>> If you *were* able to do the above (as an admin), would you still have >>> the same issues with this proposal? >>> >> No, If that were true, I could live with this proposal. I would at >> least have the ability to do what I want. > > > So, let me toss out a proposal: > > OSS stuff (purposely undefined here :-) shall install into > somewhere other than /usr/bin. The various directories > discussed here (/usr/sfw, /usr/gnu, /opt/wherever) are all > potential locations; the exact location for a particular > instance of "OSS Stuff" is intentionally not specified here. > > ALL package dependencies are required to be on the above > packages; all PATH dependencies are required to be on the > above install locations. > > There shall also exist a "symlink convenience package" > for each "OSS Stuff" that (following the "no conflict" rules > mentioned elsewhere in this thread) makes symlinks in > /usr/bin. NO components may depend on the existence of > these packages or require their installation - they are > intended for use by human users only, and are expected > to be installed (or not) at the sole discretion of the > customer. > > This proposal says nothing about whether the Solaris Install > process should default to installing or not installing these > convenience symlink packages. > > -John
