bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH 0/6] build-aux/bootstrap that doesn't need to replace itself
Date: Tue, 27 Dec 2022 22:09:36 +0100	[thread overview]
Message-ID: <2347260.KlZ2vcFHjT@nimes> (raw)
In-Reply-To: <20221227190002.5660-1-eggert@cs.ucla.edu>

Hi Paul,

You write in <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56749>:

> I put the latter script into the gzip 
> repository but did not put the auxiliary files there. I did not notice 
> the error in my testing, since the three auxiliary files were there in 
> my working copy.

I'm sorry that the mechanism that I coded in July got you into making
a mistake.

But I strongly object against the backwards move regarding the autopull.sh /
autogen.sh *concepts*.

The concepts, as I described them in
are that

  * There are two preparation phases for a git repo, before the user
    can run configure: './autopull.sh' then './autogen.sh'.

  * These are *interfaces* between the package's code and the developer.
    Like the *interface* behind the 'configure' script. The purpose
    is that — over time, as more and more packages adopt these two script
    names — developers can just use these two script names as part of their

The implementation (bootstrap script, bootstrap-funclib.sh function library)
are just an implementation of these concepts. If your implementation works
better than mine (by avoiding some possible pitfalls), then that's fine.

But what I object to is that you are killing the incentive for more packages
to adopt the autopull.sh / autogen.sh separation. In particular:

  * It's better to recommend in README-hacking

        $ # 1. Fetch auxiliary files from the network.
        $ ./autopull.sh
        $ # 2. Generate files locally.
        $ ./autogen.sh

    because that's the two command names that the developer should remember
    and get used to work with.

    If you write

        $ ./bootstrap --pull  # 1. Fetch some files from the network.
        $ ./bootstrap --gen   # 2. Generate other files locally.

    then we have different command names for the same thing, and it
    encourages packages to clump two different things into a single

  * I object against omitting autopull.sh and autogen.sh from what gets
    copied into the package.

  * I object against documentation such as

        running @samp{./bootstrap --pull} or @file{autopull.sh}

    because two different commands (with 'or') does not help in creating
    a habit that is easy to remember and easy to use.


  parent reply	other threads:[~2022-12-27 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 18:59 [PATCH 0/6] build-aux/bootstrap that doesn't need to replace itself Paul Eggert
2022-12-27 18:59 ` [PATCH 1/6] Move scriptversion= lines up in scripts Paul Eggert
2022-12-27 18:59 ` [PATCH] stdnoreturn: deprecate Paul Eggert
2022-12-27 18:59 ` [PATCH 2/6] Make autogen a shell function too Paul Eggert
2022-12-27 18:59 ` [PATCH 3/6] Make autopull " Paul Eggert
2022-12-27 19:00 ` [PATCH 4/6] Bootstrap with functions, not scripts Paul Eggert
2022-12-27 19:00 ` [PATCH 5/6] Support packages with just 'bootstrap' Paul Eggert
2022-12-27 19:00 ` [PATCH 6/6] Add --pull, --gen options to build-aux/bootstrap Paul Eggert
2022-12-27 21:09 ` Bruno Haible [this message]
2022-12-28  2:16   ` [PATCH 0/6] build-aux/bootstrap that doesn't need to replace itself Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2347260.KlZ2vcFHjT@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).