passing of DESTDIR for staged installs incorrect
------------------------------------------------
Key: CBUILDS-24
URL: http://jira.codehaus.org/browse/CBUILDS-24
Project: Mojo C Builds
Issue Type: Bug
Affects Versions: 1.0-alpha-4, 1.0-alpha-5
Reporter: Lee Thompson
Priority: Minor
The latest codebase passes DESTDIR incorrectly to autotools.
DESTDIR is used to "stage" the install to a temp directory (under the maven
target directory typically) prior to packaging. Older version of plugins did
this correctly. The latest version do something like this....
$ DESTDIR=/my/staged/directory
$ make install
It should be
$ make DESTDIR=/my/staged/directory install
You can get around this by configuring your plugin something like this...
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>make-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<workDir>${workDir}</workDir>
<prefix>${prefix}</prefix>
<destDir>${pkgBasedir}</destDir>
<!-- Gets around a bug in c-builds 1.0-alpha-5
Plugin defines a DESTDIR enviroment variable instead of running
"make DESTDIR=${destDir} install" which is the documented way
to do things -->
<installOptions>
<installOption
implementation="java.lang.String">DESTDIR=${pkgBasedir}</installOption>
</installOptions>
</configuration>
</plugin>
The behavior should revert back. Newer versions of autoconf packages respond
to the environment variable, but older ones do not for some reason. Since the
command line specification is what is documented in autotools, that is what
should be done.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
