[EMAIL PROTECTED] wrote:
This thing obviously doesn't scale and in the long term we may end up
reinventing a full blown package manager with dependency tracking, plus
tools like apt for downloading and installing them.
It seems to me that the ideal thing would be for Sun to go ahead and
M. Edward (Ed) Borasky wrote:
This thing obviously doesn't scale and in the long term we
may end up reinventing a full blown package manager with
dependency tracking, plus tools like apt for downloading
and installing them.
I've spent a fair amount of time with both yum and apt and I fail
Hi,
It seems to me that the ideal thing would be for Sun to go ahead
and get around to releasing certain bits of the OpenSolaris tree
under dual GPL/CDDL [..]
If Sun wanted Linux to rip off Solaris code easily, they would have
just released everything under the GPL right
My activity reads RDF files and uses libraptor.so.1 to do that. Fedora
does package this in the raptor.i386 RPM. This package is not installed
on the Build 650 I'm using. I also see no way to specify RPM dependencies
in a .xo nor a way that deployed XOs could be guaranteed to be able to get
Asheesh Laroia wrote:
I suppose I'll have to include a libraptor.so.1 in my own .xo's lib/
directory. Is the normal(ish) way to do this by just unpacking the RPM
and yoinking the Fedora-compiled .so and jamming that file into my .xo?
This is my understanding. As long as it's just one
On Mon, 10 Dec 2007, Bernardo Innocenti wrote:
Asheesh Laroia wrote:
I suppose I'll have to include a libraptor.so.1 in my own .xo's lib/
directory. Is the normal(ish) way to do this by just unpacking the RPM
and yoinking the Fedora-compiled .so and jamming that file into my .xo?
This
Asheesh Laroia wrote:
This is my understanding. As long as it's just one library, it isn't a
big problem. I have a friend who is packaging 5MB of Mono libraries for
an activity written in C#.
That person is still your friend? (-;
Shhht! He may hear us ;-)
Right. Let me note here
This thing obviously doesn't scale and in the long term we may end up
reinventing a full blown package manager with dependency tracking, plus
tools like apt for downloading and installing them.
It seems to me that the ideal thing would be for Sun to go ahead and get
around to releasing
This thing obviously doesn't scale and in the long term we may end up
reinventing a full blown package manager with dependency tracking, plus
tools like apt for downloading and installing them.
But seriously, does the XO really need two package managers? What's
wrong with
