On Jul 21, 2005, at 7:13 AM, Joerg Schilling wrote:

Alvaro Lopez Ortega <[EMAIL PROTECTED]> wrote:


IMHO, it is the systems level thought and integration that makes
Debian more than simply a collection of pre-built packages.
Obviously, I have been quite impressed by the thought and effort
that has gone into the Debian system, and agree with David that
OpenSolaris could benifit from it.


   Yeah, that exactly what I mean.  Debian will bring a huge set of
   quality software greatly integrated to OpenSolaris.


Why do you expect that packages that only have been tested on Linux
will even compile on Solaris?

Because the vast majority of those packages have been run on a large variety of OSes including Solaris. I'm not advocating an particular packaging system (aside from Sun's), but the software products themselves will have a very high "out-of-the-box" build success rate.

The most common mistake that open-source packages make is not respecting the --libdir argument to autoconf's configure. This makes it a bit of a pain to put things in /prefix/lib/$(ISA)/ and the same thing with --bindir.

Still, "porting" efforts for the vast majority of these projects are simply build process modifications and fixing up of compiler flags and install targets. Hardly ever does it require source code modification.

What I think would be great is a FreeBSD Ports style package orchestration system... And you you type "make package" it drops a: PORTname-version.gz in an export directory for administrative consumption. The overall system would simply consist of a versioned pointer to the original source, set of patches to the source (rarely), patches to the build process (commonly), the pkginfo file and a Makefile that "does it."

Sounds spectacular to me. It's an orchestration of packages, because the entire system sits well outside of the administrative scope of the machine itself -- packages aren't "installed", just produced. You can do pkgadd, pkgrm them as you please.

_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to