| Using autoreconf leaves me without any way to work around this problem,
| unless I make a bootstrap script anyway (calling `touch README` before
| autoreconf to make the problem disappear).
Precisely. That's why I still don't understand your argument. I have
this:
| ~/src/a2ps-4.13 % cat
Akim>> Please, promote autoreconf use for bootstrapping. That way, we
Akim>> will be reported more cases, more bugs etc. which is always a
Akim>> good thing. In addition, in the future, if we add new people in
Akim>> the build system (such as the replacement of aclocal), although
Akim>> the a
On Fri, Sep 06, 2002 at 01:37:57PM +0200, Ronald Landheer wrote:
> What I'd like to know is whether it is possible to keep the GNU (--gnu)
> standards for Automake's checking, but not have it look at README while
> bootstrapping [because README is a generated file, and doesn't exist
> yet at tha
> "Ronald" == Ronald Landheer <[EMAIL PROTECTED]> writes:
>> Please, promote autoreconf use for bootstrapping. That way, we
>> will be reported more cases, more bugs etc. which is always a good
>> thing. In addition, in the future, if we add new people in the
>> build system (such as the re
In response to both Tim and Akim:
>> An obvious, though not very elegant, solution would be to bootstrap
>> like this instead:
>> --
>> #!/bin/sh
>>
>> noreadme=
>> test -f README || noreadme=yes
>> test x$noreadme = x || touch README
>> set -x
>> aclocal
>> autoheader
>> automake -i --add-miss
| An obvious, though not very elegant, solution would be to bootstrap like
| this instead:
|
| --
| #!/bin/sh
|
| noreadme=
| test -f README || noreadme=yes
| test x$noreadme = x || touch README
| set -x
| aclocal
| autoheader
| automake -i --add-missing --copy
| set +x
| test x$noreadme = x ||
On Fri, 2002-09-06 at 13:37, Ronald Landheer wrote:
> Hello all,
>
> I'm trying to bootstrap a package that is "almost" completely compliant with the GNU
>coding standards: the only difference with a normal GNU pack is that the README file
>is generated (from a perlpod file). This is meant to m
Hello all,
I'm trying to bootstrap a package that is "almost" completely compliant with the GNU
coding standards: the only difference with a normal GNU pack is that the README file
is generated (from a perlpod file). This is meant to make it easier to make the same
kind of file in a manpage (s
