> I remember a lot of the arguments for dynamically > linking programs/shared libraries/etc, but a lot of > the reasoning (disk space being one I can name > offhand) is no longer valid as it really isn't an > issue anymore.
For a server, centrally managed and installed libraries and packages is a must. The same goes for desktop users (ala SunRay). Individual desktop users may have different needs. > #1 - Application provider provides a "source package" > of sorts, which includes ALL libs/headers/whatever > needed to compile application, plus source to > application. There is a configuration script in this > package that allows you to select which/what options > you'd like to have the application built with. > Finally, there would be some kind of automated build > tool (or just simple makefiles/whatever) that would > allow a very simple build of a "binary package". > > The logic behind this is making it easy to build php > with support for X Y Z module that you need, but > nothing else. Or, easily change this later, without > worrying that the libraries/etc have changed and > you'll have incompatibility issues. Someone could provide a tool that did this now using the existing Solaris Package Format. Or you could use OpenPKG... > #2 - A (new) OSOL/Solaris package management tool; > since the applications would not be linked against > anything on the system itself, only against libraries > contained within the package, removal is easy as > well. For an automated update tool, it'd be nice to > have some kind of central registry of installed > packages, thus the "install package" and "deinstall > package" options/tools - but since they are self > contained, a simple cp or rm should suffice if people > feel the need. > > I think this kind of solution would allow application > providers to focus on their application, having > control over a lot of "variables" they normally do > not have. It would also allow system administrators > to deploy applications built as required quite > easily, completely avoiding the HEADACHES I've had to > go through to get some software > compiled/installed/etc on OSOL/Solaris. If the source > packages are created in the way I mentioned, it'd be > rather trivial to write a build tool/script/whatever > that would autobuild with the selected configuration > and generate a binary package file that could be > installed or deinstalled in one simple step. > > This would also allow the OSOL community/Sun to focus > on the OS, and let the application developers focus > on their applications, as it should be. > > I know I'm putting myself in the line of fire with > this post/mail, but I wanted to throw it out. I'm > sure other people have suggested things like this > before, but I didn't see the conversations and I > didn't notice them when I went back around 20 or so > pages. My apologies in advance if I have duplicated > another posting. Really, almost everything you ask for is answered by OpenPKG, which supports Solaris. In fact, if you combine it with apt-get, you have a nifty little solution. Since OpenPKG uses it's own package database, etc. you can easily install and remove libraries and applications without bothering the base operating system install, and because all of the applications live under their own directory tree, there are no conflicts with existing installs. -Shawn This message posted from opensolaris.org
