Re: [GNUstep-packagers] patch for observance of $HOME

[Rogelio M . Serrano Jr .]

On 2004-08-07 16:24:58 +0800 Richard Frith-Macdonald 
<richard@brainstorm.co.uk> wrote:

> I would not use such a system ... it's a strong requirement for 
> rolling out 
> systems
> for clients that the installed system be relocatable as I don't 
> necessarily 
> know
> where the client is going to install the software.  It's no use 
> having my 
> software
> relocatable if the gnustep package I bundle with it depends on 
> hard-coded 
> paths.

If the apps rely on NSPathutilities there should be no problem. I have 
an issue with runtime configs of the paths though. Whether its a 
script or a config file.

I you have say @"/tmp" as the default temporary directory then you 
have a problem. If you do tmppath = NSTemporaryDirectory() you are ok. 
In my case i added another key in NSPathUtilities so i can do  a 
"tmppath =  NSSearchPathForDirectoriesInDomains(GSTemporaryDirectory, 
NSAllDomainsMask, Yes)". Im using TemporaryDirectories in user 
directories and my login.app can clean up this directory before the 
use shell is started and also run any user specific daemon on a per 
login basis. And my network config daemon can do pretty much the same 
thing with the mask set to NSLocalDomainMask and it will use 
"/TemporaryDirectory". If you want wierd layout like 
/opt/GNUstep/System, /usr/local/GNUstep/Local then you have to modify 
the source code which is available. But dont expect your code to run 
verywhere GNUstep runs. Which pretty much breaks the spirit of GNUstep 
right? Like in linux we put everything in /usr/local/GNUstep or 
/opt/GNUstep. In windows it will be somewhere else. In my system its 
pretty much like Mac OS X. But these locations must be invisible to 
the applications because if it is not then applications will not run 
on different platforms unmodified.

I am already using gnustep-make as a make system for everything i can 
easily port from autoconf.