Hi!
>--[Greg A. Woods]--<[EMAIL PROTECTED]>
> [ On , September 6, 2000 at 21:57:04 (-0700), Russ Allbery wrote: ]
> very different in what they do. Indeed it should be possible to adjust
> ${DESTDIR} during "make install" (and it would only have effect during
> "make install"). $(prefix) specifies the *run-time* location of
> installed files, not necessarily the location they are installed to.
AFAIK, $DESTDIR is *only* used during make install. All packages using
automake 1.4 automatically support this. Nice, isn't it?
> --prefix=/usr/local
> make install prefix=/var/tmp/foopackage/usr/local
> and then move the package to the target machine [...]
> the right things should always happen w.r.t. installation locations and
> run-time locations.
Yes. If a package doesn't support $DESTDIR, this is the way to go.
> The problem with this is that it it is extremely confusing to developers
> and users alike (as can be demonstrated by analysis of many existing
> packages).
What is so confusing with this??? When specifying $prefix for configure, I
tell where it is supposed to be, with make install prefix=... I tell it
where it is supposed to be installed. Simple, isn't it?
If a package really uses $prefix during install (to create libtoolize,
phpize etc), it better understand $DESTDIR.
Isn't it a somewhat stupid idea to base $exec_prefix on $DESTDIR during
configure if it isn't even set at that time? And then, make install will
install stuff into $DESTDIR$exec_prefix. If $exec_prefix depends on
$DESTDIR, it is used twice...
Just my 0.02 EURO, everything AFAIK, etc etc.
Yours, Rüdiger.
--
http://www.ruediger-kuhlmann.de/
