Re: [bug #26437] Base should allow the usual "make && sudo make install"

[Richard Frith-Macdonald]

On 3 Oct 2009, at 23:20, Markus Hitter wrote:

> > Having just gnustep-config in the PATH is pretty useless ... I mean  
> > when
> > users install Gorm, how are they going to run it if the Gorm  
> > executable is not
> > in the PATH ?
>
> Well, either by typing "Gorm" in a terminal

That only works if Gorm is in the PATH of course.

> or by selecting Gorm from the application menu.
>
> For the former, there's a link installed by the package:
>
> $ ls -l /usr/bin/Gorm
> lrwxrwxrwx 1 mah mah 41 2009-10-04 00:01 /usr/bin/Gorm -> ../lib/ 
> GNUstep/Applications/Gorm.app/Gorm
>
> The latter, however, is the preferred method. Application menu  
> entries execute a one-line shell script, IIRC.

All of this is rather nit-picking evasion of the point though (who  
cares whether the executable is in the path directly, or via a link,  
or via a script) ...

The point is that a problem caused by a faulty installation of gnustep  
make is an issue which should be cured by installing gnustep-make  
properly, rather than by hacking everything which would normally use it.

If you want to do that by creating links or scripts to put the gnustep- 
make scripts in the PATH indirectly rather than by installing into a  
directory in the PATH or modifying the PATH to point to the directory  
you installed into, that's fine, but you *need* to put the gnustep- 
make scripts in the PATH some way, just as you need to put the gcc  
binary in the PATH some way in order to compile things.