Erast Benson wrote:
Forget about package format. :-)
M$ Windows do not have any embedded package managers at all. Answer on
your question is simple: Third party application developer *must* take
care of the issue. i.e. He must provide solution which will work on any
OpenSolaris-based distro (or on those where developer see its potential
market).
I'd just like to move that stability layer that cross-release developers
and installers can count on as far up the stack as practical. It looks
like your nevada-compat packages is a step towards eliminating an
unnecessary incompatibility. Cool!
Yeah, it is not possible in Linux world since absolute core libraries
like glibc keep changing on a dayly basis between 200+ distros. But this
is *absolutely* possible in OpenSolaris world where majority of the
libraries are controled by the single company - Sun Microsystems, Inc
and API/ABI is not subject to change that much. That means that it is
possible to create bare minimum independent binaries which will run
everywhere on any OpenSolaris-based distro. (read: installation software
like Install Shield, etc).
When you are buying Windows software you first checking if your Windows
version will work. So, you just insert CD, and setup application takes
care of differences between the versions. This is proven. This is the
way to go. IMHO
Sometime around Win2k the popular solution to "dll hell" was for all
applications to install their dlls because disk space is cheap. Package
managers give us much more flexibility and as you've seen, zones gives
us use even more interesting possibilities.
I'm looking forward to hearing how your Nevada zone works for you.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
