Re: path handling changes to try out ...

[Helge Hess]

Nicola Pero wrote:
> If you need to source GNUstep.sh before starting a tool, why not using the
> following shell script -
>
> #! /bin/sh
>
> . /opt/gnustep/System/Makefiles/GNUstep.sh
> mytool "$@"
>
> just save this as /usr/bin/mytool and then you can execute mytool from the
> command line perfectly well - without having to set up anything in
> advance, not even the PATH.

That looks perfect for the usual case. Maybe one should write a tool 
which runs in the rpm-postinstall section which collects the Tools in 
GNUstep and autocreates the wrappers in /usr/local ?

> If you don't want to set up LD_LIBRARY_PATH, please consider adding your
> gnustep paths (system/local/network) to /etc/ld.so.conf, and running
> ldconfig (but you need to do it after installing each library).  It's not
> forbidden :-) it's actually recommended if you don't have multiple
> library-combos.

Well, I have multiple library combos ;-) I'm also not talking about 
setup of my environment but rather about the deployment for 
non-developer people ! Further I would like to find a way to use the 
GNUstep environment on MacOSX without the need to call any weird MacOSX 
config files.
Maybe we talk about that at Fosdem ;-)

BTW: how am I supposed to configure for a different library combo, is 
"./GNUstep.sh gnu-fd-nil" and "./GNUstep.sh gnu-gnu-nil" supposed to work ?
[I'm going to try out gstep-base once more ;-)]

> I don't mind simplifying and improving gnustep-make startup and
> configuration if the suggestions are good and workable ... the problem is
> I don't see that much space for improvements, without loosing valuable
> features.  If you have suggestions, let me/us know.

No, don't let us loose features ! ;-)

Top-Priority addition I would wish for is the GNUSTEP_PATHPREFIX_LIST 
duplicate removable script, since it makes environments much nicer in 
setups with duplicates ...


Greetings
  Helge