discuss-gnustep
[Top][All Lists]
Advanced

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

Re: Please do not hardcode GNUSTEP_INSTALLATION_DOMAIN in GNUmakefiles!


From: Truls Becken
Subject: Re: Please do not hardcode GNUSTEP_INSTALLATION_DOMAIN in GNUmakefiles!
Date: Wed, 29 Oct 2008 00:02:11 +0100

Nicola Pero wrote:
>
>> Question to Nicola; maybe gnustep-config should be in /usr/local/bin
>> to successfully provide a bridge from standard Unix hierarchy to
>> whatever layout the GNUstep installation is using? The -make package
>> would then need two different --prefix options, which is a bit of a
>> problem.
>
> Yes - we could have a ./configure option to specify where you want to
> install gnustep-config, openapp and opentool.  If nothing is provided,
> we'd default to install them into SYSTEM_TOOLS, like we do now. :-)

Well, people expect to simply do ./configure; make; make install, and
have everything work out of the box. As long as gnustep-config
defaults to a Tools directory, the chicken-egg problem will persist;
to find gnustep-config you need to know something that you run
gnustep-config to reveal. I would think the whole point of this script
was to be available in $PATH when the environment is not yet set up?

Packagers will get things working regardless, so the main issue is
with Joe User doing a default install.

Ideally, gnustep-config would install to /usr/local/bin +
/usr/local/man and the domains to /usr/local/GNUstep. With ./configure
--prefix=/usr, they would be /usr/bin, /usr/man, and /usr/GNUstep. I
don't know how feasible this is as it would require changes to the FS
layout system. The use of $prefix currently varies between layouts.
With the gnustep one, the prefix option is on the form
--prefix=/usr/GNUstep rather than the standard --prefix=/usr, while
the apple layout assumes --prefix=/




reply via email to

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