On Wed, 02 Jul 2008 01:00:57 PDT UNIX admin <[EMAIL PROTECTED]> wrote:
> Again: the only operating system that has this solved *cleanly* is
sgi IRIX, because the inst(1M) software management subsystem works
based on the principle of namespaces.
I'd nominate most of the various BSD port systems as having solved it
cleanly, but this may be a matter of what we define as "the problem".
The real issue is this:
> And under this concept, a 3rd party packager may deliver his/her own
software anywhere on the system (naturally, /opt!) and their
packages would be automatically replaced as soon as the vendor
issued a newer revision - as long as the 3rd party packager used the
same namespace. This concept is critical and essential for solving
the current shared object libraries and application duplication in
Solaris in general, and not just OpenSolaris.
This is ambiguous. I can only think of one instance where this
behavior makes sense, but haven't dealt with IRIX to know if that's
what you mean. Basically, the only time an OS update should *ever*
muck with third party software is if the package in question was built
by someone who's using it for an out of date rev of the OS, knowing
that a later rev of the OS will provide a compatible replacement.
Other than that, upgrading the OS should leave the third party
software alone. That includes the case where I skip over any revisions
the package author designated as suitable for replacing his package.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
_______________________________________________
opensolaris-discuss mailing list
[email protected]
