How about this? I took into account Ralf's comments as well.
In addition, if you use an unusual directory layout you can give
options like @option{--bind...@var{dir}} to specify different
values for particular kinds of files. Run @samp{configure --help}
for a list of the directories
Hi Eric,
thanks for pursuing this.
* Eric Blake wrote on Wed, May 13, 2009 at 02:51:34PM CEST:
> @@ -156,7 +158,25 @@ Installation Names
> In addition, if you use an unusual directory layout you can give options
> like @option{--bind...@var{dir}} to specify different values for
> particular ki
+Depending on the package, the default directory layout chosen during
+...@command{configure} can be altered during subsequent execution of
+...@command{make}.
A `make install FOO=VAL' should never alter anything in the build
directory. The problem is if you pass --bindir=/foo to confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 4/15/2009 5:51 AM:
>> Maybe the generic INSTALL file should provide pointers to more
>> comprehensive documentation?
>
> I tend to agree that INSTALL should either mention DESTDIR (and probably
> also V, which now plays a ro
[ dropping bug-coreutils ]
Hello Alfred,
* Alfred M. Szmidt wrote on Wed, Apr 15, 2009 at 07:17:42PM CEST:
>> So for maximum portability you should support this in your
>> package, too. BTW, why do you state that overriding just $prefix
>> would be "almost always wrong"?
>
>In t
Well, you would just change autoconf so that it fails fast when its
configuration is not "well formed"...
On Wed, Apr 15, 2009 at 7:54 PM, Bob Friesenhahn
wrote:
> On Wed, 15 Apr 2009, Alfred M. Szmidt wrote:
>>
>> The problem is that DESTDIR is not a mandatory standard and
>> packages may not
On Wednesday 15 April 2009 07:06:09 Ralf Wildenhues wrote:
> > > Not all packages follow GNU Coding Standards, therefore,
> > > DESTDIR is not properly supported in a surprisingly large
> > > number of packages.
> >
> > We already enforce a level of GNUism on packages that use
> > autoconf/automake
On Wed, 15 Apr 2009, Douglas Held wrote:
Well, you would just change autoconf so that it fails fast when its
configuration is not "well formed"...
How would autoconf know that?
Currently we have 'make distcheck' which tests a distribution tarball
and entrusts that the maintainer won't distri
On Wed, 15 Apr 2009, Alfred M. Szmidt wrote:
The problem is that DESTDIR is not a mandatory standard and
packages may not adequately implement it even if Automake itself
does the right thing. If INSTALL says that DESTDIR is supported
and a package blindly includes the INSTALL file, then
> So for maximum portability you should support this in your
> package, too. BTW, why do you state that overriding just $prefix
> would be "almost always wrong"?
In the w32 arena, overriding $prefix at `make install' time is
unilaterally *correct*. Why can your staging area not mi
>>Hmmm. Would it be worth changing autoconf to make './configure
>>--help' state something like the following:
>>
>>| Some influential environment variables:
>>| ...
>>| DESTDIRleave unset during configure; allows installation
> I tend to agree that INSTALL should either mention DESTDIR (and
> probably also V, which now plays a role with new enough
> automake), or at least point to the GNU Coding Standards and the
> Automake manual overview of the GNU build system. Does anyone
> want to beat me to a patch
On Wed, 15 Apr 2009, Eric Blake wrote:
I tend to agree that INSTALL should either mention DESTDIR (and probably
also V, which now plays a role with new enough automake), or at least
point to the GNU Coding Standards and the Automake manual overview of the
GNU build system. Does anyone want to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 4/15/2009 12:06 AM:
> Please, let's not bloat `configure --help' output even more. It is
> already very long for a simple help text, it should not document things
> that are not, in fact, settings for configure but for
Hello Alfred, Eric,
* Alfred M. Szmidt wrote on Tue, Apr 14, 2009 at 02:49:30PM CEST:
>>Hmmm. Would it be worth changing autoconf to make './configure
>>--help' state something like the following:
>>
>>| Some influential environment variables:
>>| ...
>>
>packages where DESTDIR doesn't work properly. But automake
>already does such a good job at providing DESTDIR support
>(especially if the user remembered to run 'make distcheck'),
>that I think it would be nice if using AM_INIT_AUTOMAKE did
>make the ./configure
>Hmmm. Would it be worth changing autoconf to make './configure
>--help' state something like the following:
>
>| Some influential environment variables:
>| ...
>| DESTDIRleave unset during configure; allows installation to
>| spec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alfred M. Szmidt on 4/14/2009 6:49 AM:
>`To install FOO in a staging directory, use `make install DESTDIR=...''
>
> I like that.
>
>packages where DESTDIR doesn't work properly. But automake already
>does such a good job at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[really adding autoconf and automake lists this time]
According to Alfred M. Szmidt on 4/14/2009 6:22 AM:
>Hmmm. Would it be worth changing autoconf to make './configure
>--help' state something like the following:
>
>| Some influential
19 matches
Mail list logo
