On 7/20/05, Jasse Jansson <[EMAIL PROTECTED]> wrote: > > 2) Some people have limits on their bandwidth usage, or even heaven > > forbid have to pay for usage based on time or bandwidth. This means > > duplicate software is not only wasteful, it's costly... > > You just updated the old saying from > "free software is only free if time has no value" > to > "free software is only free if time has no value and high > speed internet access is available at a fixed monthly rate"
I'm not sure what relevance that comment has to this conversation, so I'll ignore it for now. > What do you want us to do instead with our spare clock cycles??? > [EMAIL PROTECTED] ??? <BIG GRIN> No, what I meant is that a lot of time and effor that could be better spent improving and porting software to Solaris is instead being spent on reinventing the wheel (i.e. repackging). > Include a startup shellscript that installs in a standard location > that is > already in the path (/usr/local ??) and include the following line > before > the actual start command: > > PATH=/path/to/needed/stuff:$PATH > > Would a simple scheme like this work in real life??? I honestly dont' know, but my gut feel is that it wouldn't be sufficient, it would be simpler just to install into standard locations instead of an isolated directory tree. > > Ideally, a user should be able to click a link, or download a package > > from disparate sources, and installation should just work. That's what > > happens on other systems like Windows or Mac OS X today for the most > > part. This package hell must end :) > > Both Windows and MacOS X has only one source of updates. Easy choice. If you're talking about the OS, yes. But I'm not talking about the OS so much as I'm talking about 3rd party software. In that case there is not one source of updates, and there is not an easy choice. > But I have the impression from the discussions in this maillist, that > everyone > want an unified package system, as long as it's their own favorite. > Opensource developement in a nutshell, I say. Facts of life I guess. I initially favored OpenPKG simply because it was great to work with and I didn't see anything similar for Solaris' built in packaging tools. However, pkgbuild.sf.net a project maintained or written by some SUN engineers works great. As far as "favorite packging system", my vote is for what Solaris has. It makes working with the Solaris packaging tools almost as easy as working with RPMs, and certainly easier than creating Debian packages (in my personal view). Regardless of "favorite package system", I still think there's a way to at least mitigate or reduce some of the problems caused by these duplicate software stacks. It just requires some agreement and compromise among the parties involved. -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
