On Tuesday 11 March 2008 17:22, Curtis Olson wrote:
> On Tue, Mar 11, 2008 at 12:06 PM, Melchior FRANZ wrote:
> > No, you can leave that. Just install plib somewhere else (e.g.
> > in your home dir), and point sg and fg to it via
> > --with-plib=... plib is (supposed to be) linked statically, so
> > it's not needed at runtime and can be anywhere.
>
> Just be careful ... multiple versions of libs can coexist just
> fine in different places on your hard drive, but if in a couple
> months, you forget how you set it up, or just lose focus
> momentarily, you could end up building against the wrong version
> of the package (or even headers from one version and libs from
> another, etc.) and end up with some weirdness ... so it's always
> best to recognize your own limitations and weaknesses and decide
> if you want more than one version of a lib on your system at one
> time. :-)
>
> There are many ways to make this easier or harder on yourself ...
> I won't get into all the sysadmin details, but as a general rule
> of thumb, I personally try to avoid having pre-packaged versions
> of software installed on the same system as a different version
> built from source ... as long as I can sidestep the dependency
> hell of the linux packaging system to remove a particular
> package.
>
> Regards,
>
> Curt.

Yup, that's exactly what was going through my mind.  Luckily, I 
don't have anything other than FG that's dependant on plib so I can 
uninstall the packaged version without problems - phew:)

It's just that I have seven machines to maintain, each with two 
entirely separate O/S copies on them, for testing, resilience & 
recovery reasons, the second copy on each machine being 
a 'held-back' known-to-be-working stable version of the first.

It means fourteen systems, at two different s/w levels to maintain 
and keep track of, which isn't trivial.  Heh:) - when I was running 
Debian 'unstable' I had three systems on each machine, because 
upgrade breakages were quite common.  However, since switching 
to 'stable' I've been able to reduce it to two:)

Just in case anyone's wondering, I usually only have three or four 
systems running for FG stuff - one or two 'workstations', a server 
and a gateway/firewall.  The others only really get used for 
distributed 3d rendering and upgrade installation testing, although 
every system has a copy of the the server data and gateway/firewall 
configs backed up on to it so I can quickly swap a system in/out if 
there's a serious h/w problem anywhere.

LeeE

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to