Prev: convert CPU load to CPU utilization in %
Next: SunRay with different displays
From: David Kirkby on 1 Jan 2010 16:16
On Dec 16 2009, 10:31 pm, groen...(a)cse.psu.edu (John D Groenveld)
wrote:
> In article <hgbedv$8...(a)reader1.panix.com>,
>
> David Combs <dkco...(a)panix.com> wrote:
> >So I (and I guess most users too) would like to have some
> >from you, and some from blastwave, depending on the versions.
>
> Assuming you're attempting to use CSW packages as dependencies
> for your SageMath builds, set up two zones: one with pkg_get pointing
> towards OpenCSW and another pointing towards Blastwave.
>
> John
> groenv...(a)acm.org

You might be confusing two Dave's there.
From: phil.googlenews on 4 Jan 2010 14:15
On Dec 30 2009, 8:47 pm, dkco...(a)panix.com (David Combs) wrote:
>
>
> Phil -- could you be a bit more specific about the precise changes
> one has to make to the current blastwave pkgutil to access opencsw
> stuff?

sure, there's multiple ways.
Just go edit whatever line you changed to set your choice of blastwave
repository, and change it to point to an opencsw one.

Or use commandline flags for one-time use. Dunno about pkgutil, but
pkg-get uses
pkg-get -s url://goes/here.



>
> Another question: by playing with a symlink, defining it one
> way when wanting to deal with blastwave, and a second way
> when dealing with opencsw -- any way something like that
> could enable a system to have both available.
>
> I suppose when you wanted to USE a package, or a set of packages,
> you would have to use packages from only one or the other --
> else internal refs would be to the wrong place?

Yeah, it would be ugly. because of dynamic library runpaths. which
will want to use /opt/csw.

ERRRR.. i SUPPOSE you could manually override with LD_LIBRARY_PATH.
strongly unrecommended.
However, there is also the issue that many programs expect to find
configurations under /opt/csw also.

You'd have to re-symlink, or re-loopback-mount, /opt/csw, every time
you wanted to change repository.

Or use chroots.
Or zones.





> Or even some kind of a perl or sed filter we can run a
> opencsw package through and change every csw to opencsw?

There is no easy way to do that, i'm afraid, because of the need for
binary editing.
if you wanted to do it the HARD way and rig something up, you might
potentially work it, if you wanted to have an alt dir with exactly the
same length. so, "/opt/csw", and "/opt/CSW" perhaps,... and then you
could substitute all occurrences relatively safely.


But you're really better off by looking at your needs, and seeing
which organization meets your needs better.
Hypothetical example of method you might use to make your choice:

Lets say that you need 3 programs; progA, progB, progC.

both sites have progA up to date
site1 has progB newer, and you want the newer.
site2 has progC newer, and you want the newer.

So, contact site1, and say, "hey how about an update to progB?"
also, contact site2, and say, "hey how about an update to progC?"

Go with whichever one gives you the update faster/better :-)

>We are all -- at least us users -- better off were, say,
>Ford and GM, etc, to make their cars such that a piece
>of equipment from one would work on the other.

Eh... only because that means shared parts are "cheaper" for you to
buy. But in this case, both are "free", so ... :-)

(and in some respects, users have been worse off with shared parts in
cars: "Both Suck!" :-D )



First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: convert CPU load to CPU utilization in %
Next: SunRay with different displays