Re: improve INSTALL contents

can you please also read, and follow ? I'm sure you must have missed it because I failed to spam it to three mailing lists. But your repetitions are just as boring as those from everyone else. And get bug-coreutils a

Re: improve INSTALL contents

Alfred, can you please also read, and follow ? I'm sure you must have missed it because I failed to spam it to three mailing lists. But your repetitions are just as boring as those from everyone else. And get bug-coreutils and aut

Re: improve INSTALL contents

Indeed - I want to be very clear in INSTALL that there are some basics that pretty much any client of this file provide (make, make install), and some options that nice packages provide but which may fail if someone borrowed this file but does follow everything checked by automake's

Re: improve INSTALL contents

>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 you can set and what kinds of files >

Re: improve INSTALL contents

>> What about packages that don't support arbitrary prefix override >> (all those using current libtool), or packages or systems that >> don't support DESTDIR installs? This wording creates problems >> for them. > > Indeed - I want to be very clear in INSTALL that there are some

Re: improve INSTALL contents

On Fri, 15 May 2009, Eric Blake wrote: What about packages that don't support arbitrary prefix override (all those using current libtool), or packages or systems that don't support DESTDIR installs? This wording creates problems for them. Indeed - I want to be very clear in INSTALL that there

Re: improve INSTALL contents

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 5/15/2009 12:00 AM: > * Alfred M. Szmidt wrote on Fri, May 15, 2009 at 04:45:21AM CEST: >>In addition, if you use an unusual directory layout you can give >>options like @option{--bind...@var{dir}} to specify dif

Re: improve INSTALL contents

* Alfred M. Szmidt wrote on Fri, May 15, 2009 at 04:45:21AM CEST: >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 d

Re: improve INSTALL contents (was: Core-utils 7.2; building only 'su')

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

Re: improve INSTALL contents (was: Core-utils 7.2; building only 'su')

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

Re: improve INSTALL contents

>+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 y

Re: improve INSTALL contents

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Alfred M. Szmidt on 5/13/2009 7:22 AM: >+Depending on the package, the default directory layout chosen during >+...@command{configure} can be altered during subsequent execution of >+...@command{make}. > > A `make install FO

Re: improve INSTALL contents (was: Core-utils 7.2; building only 'su')

+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

improve INSTALL contents (was: Core-utils 7.2; building only 'su')

-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