INSTALL mentions "bootstrap" file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



(link to archived email:
https://lists.gnu.org/archive/html/autoconf/2023-08/msg00011.html).

On Fri, Aug 18, 2023 at 10:02:53PM -0500, Paul Eggert wrote:
> > In the Texinfo package, the script is called "autogen.sh".  I doubt that
> > it offers more "fine-grained control" (as stated in the current text of
> > INSTALL) but appears to be just another name for this script.
> 
> That part of the documentation is talking about the practice, supported by
> Gnulib, of having two bootstrapping scripts.  One, autopull.sh, fetches
> stuff from the network (and therefore has network and privacy concerns); the
> other, autogen.sh, is purely local. Often 'bootstrap' does both but you can
> run just one script or the other.
> 
> Another common practice is for 'bootstrap' to have --pull and --gen options,
> to do (network-based) pulling and (local-based) generation, instead of
> autopull.sh and autogen.sh, and where if you don't use either --pull or
> --gen than 'bootstrap' does both. Gnulib supports this too.
> 
> 
> > Is there any consistency in naming across different packages, i.e.
> > is "bootstrap" the most widely used name?
> 
> Hard to say. I prefer 'bootstrap' but there's definitely an 'autogen.sh' and
> perhaps 'autopull.sh' camp. Which is why Gnulib supports both.

The text of INSTALL still uses "bootstrap" even though not all packages
use this file and there is no reason that they should.

This is causing confusion for users:

https://lists.gnu.org/archive/html/help-texinfo/2024-09/msg00009.html

From:	Rudolf Adamkovič
Subject:	Re: How to add "Up:" to Texinfo navigation bar?
Date:	Thu, 05 Sep 2024 16:11:03 +0200

> P.S. The `INSTALL.generic' file opens with
> 
>   Basic Installation
>   ==================
>   
>      The following shell commands:
>   
>        test -f configure || ./bootstrap
>        ./configure
>        make
>        make install
> 
> but there is no `boostrap' file.  I eventually figured out what to do,
> but it added unnecessary friction.  As a person with "fresh eyes", I
> figured I should let you know about the problem.




[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux