discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make sysinstall/Makefile.preamble/GNUSTEP_INSTALLATION_DOMAIN


From: David Chisnall
Subject: Re: make sysinstall/Makefile.preamble/GNUSTEP_INSTALLATION_DOMAIN
Date: Mon, 15 Dec 2008 11:26:16 +0000

On 15 Dec 2008, at 11:18, Richard Frith-Macdonald wrote:


On 15 Dec 2008, at 11:00, David Chisnall wrote:

I still don't fully understand the rationale for moving system packages out of System.

That would be because system packages haven't been moved out of System there's no plan to ever move them.

Okay, that's good to here.

What's happened is a change to avoid people (GNUstep newbies in particular) accidentally overwriting system packages with their non- system locally built versions.

Often this is the desired behaviour when building locally. If I have installed GNUstep from ports then compile it myself, I want applications installed subsequently, from ports or manually, to link against the new version, since it typically works better than the old one (and if it doesn't, then I can look for bugs more easily if more things are using it).

Perhaps the best solution would be to provide a script which set the prefix. When compiling stuff myself that I don't want to interfere with system packages, I typically run configure --prefix=/opt/ $PACKAGE_NAME (it's a bit of a SysV thing to do, but simplifies things a lot).

Presumably I can do the same thing with GNUstep Make and just make sure I source the correct version of GNUstep.sh from there? I've not actually tried having two copies of GNUstep Make installed, so I'm not sure...

David




reply via email to

[Prev in Thread] Current Thread [Next in Thread]