Eric Blake wrote:
> > Find attached a patch that implements the first part of it. The
> > second part will be the handling of CLEANFILES and MOSTLYCLEANFILES.
>
> No attachment, but I see you applied the patch?
Indeed, the attachment got lost when I had to resend the mail, due to
earlier mail pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 3/19/2007 6:19 PM:
> Jim Meyering wrote:
>> Another feature: bootstrap adds .cvsignore and .gitignore
>> entries for files it supplies.
>
> Good idea. It has annoyed me as well, but never reached the necessary pain
> level
Jim Meyering wrote:
> Another feature: bootstrap adds .cvsignore and .gitignore
> entries for files it supplies.
Good idea. It has annoyed me as well, but never reached the necessary pain
level. Find attached a patch that implements the first part of it. The
second part will be the handling of CLE
Jim Meyring wrote:
> My impression is that few (if any) of the autogen scripts use gnulib
The one in gettext does.
> there's another definition (the first one when I type "dict bootstrap")
> that is more evocative: to load and initialize the operating system on
> a computer. Normally abbreviated
Bruno Haible <[EMAIL PROTECTED]> writes:
> Can you try to solve both problems through overrides in
> coreutils/gl/modules/gettext.diff and coreutils/gl/m4/* ?
> If you get that working, I can see what needs to be changed in gnulib's
> gettext module. In the current state, I don't even have a preci
configure, make, etc. operations should be remove by "make
maintainer-clean".
It occurs to me that perhaps it is desirable to split maintainer-clean
(keep it as it is) and (say) bootstrap-clean after all. I can imagine,
as a maintainer, wanting to rm everything *except* the bootstrap stuff
-
[EMAIL PROTECTED] (Karl Berry) wrote:
> The only reason maintainer-clean typically has not removed files like
> configure and Makefile.am is that they have been (until relatively
> recently) version controlled.
>
> That doesn't seem quite right to me. Makefile.am is typically
Whoops.
The only reason maintainer-clean typically has not removed files like
configure and Makefile.am is that they have been (until relatively
recently) version controlled.
That doesn't seem quite right to me. Makefile.am is typically
version-controlled and always has been; furthermore, con
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
...
>> A missing feature: files supplied by gnulib-tool should be
>> removed by "make maintainer-clean". If gnulib-tool doesn't
>> do that soon, I'll be changing bootstrap to do it.
>
> It belongs in gnulib-tool, so please change gnulib
Ben Pfaff wrote:
> Bruno Haible <[EMAIL PROTECTED]> writes:
>
>> GNOME and some other GNU projects use the name 'autogen.sh' for scripts with
>> this purpose. It's a well-known and self-explaining name. I'd suggest to
>> rename 'bootstrap' to 'autogen.sh'.
>
> One oddity of the name "autogen.sh"
Bruno Haible <[EMAIL PROTECTED]> writes:
> GNOME and some other GNU projects use the name 'autogen.sh' for scripts with
> this purpose. It's a well-known and self-explaining name. I'd suggest to
> rename 'bootstrap' to 'autogen.sh'.
One oddity of the name "autogen.sh" is that there is a GNU
proje
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyring wrote:
>> My impression is that few (if any) of the autogen scripts use gnulib
>
> The one gettext does.
>
>> there's another definition (the first one when I type "dict bootstrap")
>> that is more evocative: to load and initialize the operatin
Jim Meyering <[EMAIL PROTECTED]> writes:
>> Second, the script applies gnulib-tool on a scratch subdirectory. This is
>> worrisome: it indicates that gnulib-tool does some things the wrong way.
>> Can you or Paul explain what is missing in gnulib-tool's working?
>
> I wouldn't say it's wrong, just
Bruno Haible <[EMAIL PROTECTED]> wrote:
>> Variants of this bootstrap script are being used in at least 6 or
>> 7 different projects, and having it here seems like the best way
>> to keep everyone up to date. However there's plenty of room for
>> improvement.
>
> Well, I'd suggest two improvements
Hello Jim,
> Variants of this bootstrap script are being used in at least 6 or
> 7 different projects, and having it here seems like the best way
> to keep everyone up to date. However there's plenty of room for
> improvement.
Well, I'd suggest two improvements:
First, the name. "Bootstrapping"
15 matches
Mail list logo
