%% Russ Allbery <[EMAIL PROTECTED]> writes:
ra> DESTDIR is unusable for this purpose, because DESTDIR would attempt to
ra> install into /afs/.ir/pubsw/Development/autoconf-2.13/usr/pubsw/bin.
ra> That's wrong. That's not the structure of our package volumes. And
ra> there's no way of telling DESTDIR to do the right thing without changing
ra> where autoconf expects itself to be after it's installed.
Either I misunderstood what you said, or that's not quite right.
DESTDIR is added as a prefix to every _installation_ path, but it's
never used to modify any hardcoded directories. That is, if you run
"./configure; make; make install DESTDIR=/foo" then everything will be
installed into /foo/usr/local _but_ any paths hardcoded in the
application (including shared library search paths, etc.) will still be
looking at "/usr/local", not "/foo/usr/local".
I can see that you are getting extra levels of directory you don't want,
and I'm not saying we should punt $prefix (in my experience more
packages actually support overriding $prefix correctly than support
DESTDIR correctly...) I'm just clarifying what DESTDIR does.
I use DESTDIR here, even though the directory structure (a homegrown
symlink thingy) isn't what I want; I use DESTDIR to install it
elsewhere, then I physically mv the installed directories around to
where I want them to go. So it doesn't install correctly on its own,
but it's typically just the short work of 3 or 4 mv operations to stuff
it where it needs to be.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
