Actually, I think the configure “prefix” feature should be deprecated.
Software should be written to find everything it needs at runtime relative to the path of the invoked binary.
On Tue 2012-04-10, at 02:27 AM,
ams@... (Alfred M. Szmidt) wrote:
>> [
Dave@... - Mon Apr 09 18:50:57 2012]:
>>
>>
http://www.gnu.org/prep/standards/html_node/Standard-Targets.html>>
>> Where would I communicate the request that the above standard should
>> include a “binary-distribution" target that deletes everything except
>> files necessary for a “build install”.
>>
>> For example, I would build gcc on one server, then do a “make
>> binary-distribution”, then rsync it to other servers, where I can
>> to a make install.
>>
>> To go along with this, there should be a make target that builds
>> a runtime-requirements file, containing an inventory of
>> everything that will be required for the package to run, and
>> there should be a program that compares the information in
>> runtime-requirements with the current system to diagnose any
>> problems that might interfere with an install.
>
> You can easily do this using `make install DESTDIR=...' where DESTDIR
> specifies a temporary directory. E.g.
>
> ./configure --prefix=/usr/local
> make install DESTDIR=/tmp/FOO
> tar -C /tmp/FOO -cvf /tmp/FOO.tar .
>
> Now you can easily install something.tar on your systems in
> /usr/local; or even rsync /tmp/FOO to your targets.
>
>
