Re: make sysinstall/Makefile.preamble/GNUSTEP_INSTALLATION_DOMAIN

[Nicola Pero]

> I'm sorry, to me this still looks too complicated. Instead of having  
> a centralized
> package "database" somewhere, just check for an optional  
> configuration file (e.g.,
> installation_domain) that is present in the package's directory. If  
> present, its
> contents becomes the value of GNUSTEP_INSTALLATION_DOMAIN, if absent  
> the default
> installation domain (i.e. LOCAL) is used. That way everybody can  
> easily set up his
> or her own set of core packages and there is just a minimal change  
> in one place.
> (Okay, the svn:ignore property of the GNUstep packages might be  
> updated in order to
> reduce likelihood of somebody accidentally adding this file to the  
> repository ...)

Yup ... good suggestion :-)

... the problem I can see is that if you check out, say, gnustep-gui  
again
from scratch, your previous preference of having it install into  
System would disappear
and you'd have to set it up again :-(

The other problem is that if you go into a subdirectory of gnustep-gui  
and install only
that subdirectory, unless you have an installation_domain file in each  
subdirectory,
your domain installation preference would be ignored and you'd end up  
with stuff
in the wrong place.

I thought a single central configuration file would be the simplest  
option and would
prevent such problems.

(on the other hand, your suggestion means you can have multiple copies  
of gnustep-gui
checked out that install into different domains ...)

Thanks