[pkg-GNUstep-maintainers] Installation location

[Eric Heintzmann]

On 2004-06-20 04:19:44 +0200 Dan Weber <dan@mirrorlynx.com> wrote:

> Here is a slightly better idea.  Write a script to autogenerate 
> loader 
> scripts for /usr/bin that way you can remove all the hell from using 
> openapp. 
>   This may seem more plausable.

Most gnustep apps already provides this kind of wrapper scripts...

But using "openapp <appname>" doesn't seem to me like a hell.
Maybe are you talking about sourcing GNUstep.sh before calling openapp 
? (". /usr/lib/GNUstep/System/Library/Libraries/Makefiles/GNUstep.sh")
In this case, it would be possible to provide a wrapper script for 
openapp (and opentool too).

But since upstream recently talked about removing gnustep-make 
dependency for gnustep apps (openapp is provided by gnustep-make), I'm 
not sure that is a good idea to work on gnustep-make now.

>> On 2004-06-18 01:23:16 +0200 Dan Weber <dan@mirrorlynx.com> wrote:
>> 
>>> Non-standard installation is very ugly.  I have think you should 
>>> switch to 
>>> a more appropriate layout as the following.
>>> 
>>> /usr/GNUstep/{bin,lib,foobar}
>> 
>> 
>> It is no more FHS compliant.
>> If I look here : 
>> http://www.pathname.com/fhs/pub/fhs-2.3.html#THEUSRHIERARCHY
>> i can't find a /usr/GNUstep...
>> 
>> 
>>> 
>>> There is no reason for binaries to be under a library folder, not 
>>> to 
>>> mention its nowhere near close to FHS compliance.
>> 
>> If I watch here : 
>> http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA
>> I can find this:
>> "Applications may use a single subdirectory under /usr/lib. If an 
>> application uses a subdirectory, all architecture-dependent data 
>> exclusively used by the application must be placed within that 
>> subdirectory."
>> 
>> So it seems that /usr/lib/GNUstep is more compliant than /usr/lib 
>> (But not 
>> fully, I agree)
>> 
>>> This requires a few changes to gnustep-make and I can write a 
>>> script to 
>>> clean up installs.  The script will be debhelper compatible.
>> 
>> 
>> No, it requires important changes in upstream code of GNUstep.
>> If you change only dirs, GNUstep apps will never start.
>> 
>> But if you really want to do these changes, there is some people 
>> interested 
>> upstream.
>> Try to post something at discuss-gnustep@gnu.org
>> 
>> There is also an incomplete patch, see this post :
>> http://lists.gnu.org/archive/html/discuss-gnustep/2003-10/msg00283.html
>> 
>> Eric
>> 
>> 
> 
>