[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #24673] Gorm installs into SYSTEM by default
From: |
Nicola Pero |
Subject: |
[bug #24673] Gorm installs into SYSTEM by default |
Date: |
Thu, 27 Nov 2008 15:46:19 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.2) Gecko/2008092418 CentOS/3.0.2-3.el5.centos Firefox/3.0.2 |
Follow-up Comment #2, bug #24673 (project gnustep):
Packagers can do whatever they want, because they are experienced
users whose main job is to work on installation stuff. Hopefully
they will easily find out about the GNUSTEP_INSTALLATION_DOMAIN
flag and can install wherever they want. :-)
It's normal users who are disadvantaged by the current setup.
If they download a new version of Gorm from the internet and
install it to try it out, it will overwrite the Gorm version
that came with their GNUstep distribution (eg, Debian or
whatever GNUstep distribution they're using - including one
that puts things into /usr/GNUstep). Because 'normal users'
are, well, normal users, it may be hard for them to figure
things out - and permanently destroying/overwriting packages
that came with their OS System installation is really
unfriendly towards them! ;-)
Eg, if they have installed GNUstep using some easy-to-use
startup or installation packaging system, they'll already
have a version of Gorm in /usr/GNUstep/System. If they
download Gorm and build it manually from source from the
internet to try out a new release, it should go into
/usr/GNUstep/Local without overwriting their
/usr/GNUstep/System installation.
If they mess up with their source code hack, they can always
delete the stuff from /usr/GNUstep/Local to go back to
their System distribution. :-)
The reason everything used to be installed into System when
compiling from source is just that we never had or supported
RPMs or DEBs or any type of GNUstep distribution other than
compiling from source. As we move towards supporting more
and more easy-to-use GNUstep packages and installation options
for new users, we should be more careful about these things
and try to make sure compilation/installation from source
doesn't conflict with these packages and ready-made
startup/installation options that we're trying to breed. :-)
So, we need to start making a difference between Local and
System and understand that you install in System when you're
building a system, and you install into Local if you're
building your own local version of some package.
Thanks
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?24673>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/