[bug #24673] Gorm installs into SYSTEM by default

[Nicola Pero]

Follow-up Comment #3, bug #24673 (project gnustep):

By the way, the real question should be - why is Gorm
overring the defaults and forcing installation into SYSTEM 
instead of letting the user decide ?

Installation into SYSTEM is extremely surprising and unfriendly
if you download a source package.

Imagine if you were able to download Apple's AppKit source code
to compile it and you'd install it to try your own built of
the latest AppKit (or XCode or whatever).  Would you want it
to automatically destroy your normal AppKit/XCode installatoin
so that if it doesn't work you'll have to reinstall your
entire OS again, or would you rather have it install in
some "Local" domain where you can try it out but if it
doesn't work you can always remove the directory and go 
back to your System installation ?

This is exactly what we're talking about here.  Someone has
got GNUstep installation - probably from packages or a
distribution or a startup system or his OS, and downloads
Gorm (or gnustep-gui or something else) source code to try 
out the latest version.  Are we going by default to destroy
his GNUstep installation with his experimental build - so that
he'll have to reinstall all of GNUstep and possibly the entire
OS if it's a GNUstep-based OS, or are we going to put the 
experimental build into Local so that they can still go back to 
their normal System by just removing the Local stuff ?

Thanks

    _______________________________________________________

Reply to this item at:

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

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