not exactly a bug, but a really annoying thing

[Mauro Panigada]

I had installed gnustep-base 1.16 few times ago. It was my first
fresh from source installation of GNUstep; of course I followed
all the step described here:
http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep-howto_3.html

Today I've seen that a new version of gnustep-base (and gnustep-gui and 
gnustep-back)
was available, so I downloaded them ... I supposed everything should
have been smooth as for my first installation. But I was wrong.

After a fast reading, I decided to feed the configure script with
--prefix=/usr
since it was the configuration from the previous installation, that went into
/usr/GNUstep, and with
--with-installation-domain=SYSTEM
since it was the previous configuration, I did not want to change it, and
it sounds quite logical (if GNUstep Base is not a "system" stuffs, whatelse is?)

My common behaviour when using the configure/make/make install procedure is
to run the first two command as common user, and the switch to root just for
the installation part.

The configure was ok, with my own specified prefix and domain. But when I
run make, output says

        if [ SYSTEM != LOCAL ]; \
        then \
          GNUSTEP_INSTALLATION_DOMAIN=LOCAL ./config.status --recheck; \
        fi 

and the configuration sequence is run again! Overriding *my* decision.
I've found someone else talking about this topic, and read also a weak
answer about reasons (like newbie who "need" to see things installed into
Local when installing from sources...)


It should be the following way: if I do not specify any options to
configure, the "newbie" mode (Local domain) can be activated as
new standard installing place.

But If one, purposely, specify another domain, the configure,
and the makefiles, must honour the request.

To add confusion to confusion, the configure script at the very
beginning says:

checking for System Applications directory... /usr/GNUstep/System/Applications
checking for System Admin Applications directory... 
/usr/GNUstep/System/Applications/Admin
checking for System Web Applications directory... 
/usr/GNUstep/System/Library/WebApplications
checking for System Tools directory... /usr/GNUstep/System/Tools
checking for System Admin Tools directory... /usr/GNUstep/System/Tools/Admin
checking for System Library directory... /usr/GNUstep/System/Library
checking for System Libraries directory... /usr/GNUstep/System/Library/Libraries
checking for System Headers directory... /usr/GNUstep/System/Library/Headers
checking for System Documentation directory... 
/usr/GNUstep/System/Library/Documentation

creating the illusion that it has "understood" what I wanted (and maybe found
also my previous installation so that the result could be an updating?)

Now I must go and clean a "double" installation of gnustep-base; I will try
to uninstall both and reinstall all the 4 "start" packages from scratch,
hoping that this won't mess up other installation (like ProjectCenter, Gorm,
and some more)


-- 
Mauro Panigada
 
http://www.capo-nord.org/soci/xmav
http://del.icio.us/miyamotomusashi
 
Associazione Capo Nord
http://www.capo-nord.org
 
Risorse TeX
http://www.tug.org
http://www.guit.sssup.it/
 
FSF+GNU
http://www.fsf.org
http://www.gnu.org

"And there's a mighty judgment coming
But I may be wrong"