|
From: | Nicola Pero |
Subject: | Re: ./configure --with-installation-domain |
Date: | Tue, 6 Jan 2009 23:15:02 +0000 |
No, the whole point of the changes is so that a newbie gets stuffinstalled where they expect, so we've altered things to install in thelocal domain by default when building from source, like every other free software package out there.Where exactly is the 'Local' domain in this case ? I hita pproblem yesterday where I configured with domainb system - whcih workedfine, but tthen when I tried to build it toold me the domaisn didntmatch and re-ran configure/. I never managed toget it compiking properlyand ended up copying over and older tree. Slightly bewildered by it to be honest...Good point. I suppose ./configure --with-installation-domain=xxx should also add GNUSTEP_INSTALLATION_DOMAIN = xxx to the GNUmakefiles.
OK ... I spent more time trying to polish the new code.If you're not using relative paths - ie, in your case - and you have specified an installation domain at configure time, it will now be automatically used at install time unless you override it again at install time. :-)
If you're using relative paths - ie, most likely only on MinGW at this stage - I replaced the automated reconfigure with a detailed (and I hope clear) explanation of how to fix the problem. The problem is that we don't know which of the two conflicting domains (configure or install one) is the right one; eg, if you specify nothing at configure time, it's possibly the one specified at install time, but eg. in your case it's the configure time one instead. I think it's best to explain clearly to the user what
the problem is, and they can fix it, which is very easy. It's all in trunk, please report any issues. :-) Thanks!
[Prev in Thread] | Current Thread | [Next in Thread] |