Re: Installing A-A-P with a non-existent PREFIX

> > Does PREFIX work against everything (@install_files), or just against
> > the default list of targets (install-data, install-exec,
> > install-include, etc)?
> It works for everything.
> > DESTDIR will automatically process for @install_files, right?
> Yes.
> You can set $PREFIX to an empty string, but this has the meaning of
> installing in /usr/local.  To really install in the root directory set
> it to "/".
> 
> Is it a problem that install_files() always prepends $DESTDIR/$PREFIX
> to the directory passed to it?

The only small worry I have is

PREFIX = /
DESTDIR = /

and winding up with a system call

cp somefile ///usr/work/somewhere/.

I think '//' and '///' is unclean, and vaguely
recall it not being processed well by certain
OS platforms or software applications.

For example, if I were to use A-A-P to
list the target files and it gave '//usr/somewhere/'
that might cause things like RPM v3 to hiccup
(in my experience).

Not a big deal and maybe A-A-P is self-cleaning
in this regard with specifying the target paths.
That's the only problem I might imagine.  Otherwise,
I greatly like the dual prefixing modality provided by
DESTDIR and PREFIX.

//Scott///




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn