[bug #24670] gnustep-base installs by default in SYSTEM

[Nicola Pero]

Follow-up Comment #6, bug #24670 (project gnustep):

> Would it be unreasonable for make to detect when it is being used on an
existing 
> system and act appropriately?

It's not unreasonable. :-)

One compromised solution that I may like is have a new ./configure option
for gnustep-make.

That option would basically decide if gnustep-make should install core
packages into System or Local.

By default, we set that option to install core packages into System.  So the
big
pool of existing GNUstep users that build everything from source (starting
with gnustep-make upwards) won't see any changes. :-)

But I'd expect that packagers would change that option to disable that
behaviour when they create gnustep-make packages.  So if you are using a 
gnustep-make preinstalled by your distribution (which presumably then comes 
already with gnustep-base and other really core packages) if you install
stuff 
from source, it would then always go into Local and not overwrite your
distribution's stuff. :-)

Would that be a reasonable compromise ?  It should address the issues you
raised, preserve the current behaviour for hard-core GNUsteppers, but still
make life easy and predictable for the new GNUstep users.

I'm wondering if maybe the core packages should set not
GNUSTEP_INSTALLATION_DOMAIN but some other variable which is more clearly
linked to this option, like BELONGS_TO_CORE or some other name. :-)

Thanks


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?24670>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/