Bruno Haible writes:
> Hi all 'bootstrap' users,
>
> Over the last few years, it has become more and more clear that bootstrap
> does two things:
> (1) Fetch auxiliary files that are not in the git checkout.
> This is the part that requires network access and that has
> supply-chain
Bruno Haible writes:
> Hi dear GNU libidn developers (Simon et al.),
..
> These adjustments will be needed the next time you use the '--bootstrap-sync'
> option.
Thank you Bruno -- should be fixed in libidn git now.
/Simon
signature.asc
Description: PGP signature
On 7/30/22 22:47, Bruno Haible wrote:
Does the new documentation ([1], case 2, sub-case (C), as well as case 3)
cover Emacs adequately?
Yes, Emacs uses case (3), mostly I think because nobody but me wanted to
worry about integrating with Gnulib.
Paul Eggert wrote:
> For what it's worth Emacs has its own autogen.sh. But it doesn't use
> 'bootstrap' so I expect it won't collide.
Does the new documentation ([1], case 2, sub-case (C), as well as case 3)
cover Emacs adequately?
We can't go into all details here, because there is significant v
On 7/30/22 16:43, Bruno Haible wrote:
There is no actual collision, because your tool is 'autogen' [1],
and this is 'autogen.sh'.
For what it's worth Emacs has its own autogen.sh. But it doesn't use
'bootstrap' so I expect it won't collide.
On 7/30/22 16:43, Bruno Haible wrote:
I offered to help Miguel de Icaza with his Gnome project,
he didn't want the help, but did adopt my project's name.
Oh, so the similarity between the names is not completely fortuitous.
But meanwhile the name has spread; it is now even used in the Linux
Hi Bruce,
> >> The second phase is a script 'autogen.sh'.
>
> I'd like to object to that name. :)
There is no actual collision, because your tool is 'autogen' [1],
and this is 'autogen.sh'. Also, since a significant percentage of the
users don't have '.' in $PATH, the instructions say to run './
On 7/30/22 13:45, Simon Josefsson via Gnulib discussion list wrote:
Wonderful, thank you! I have yet to digest everything, so I'll fall
back on stylistic comments:
The first phase is a script 'autopull.sh'.
The second phase is a script 'autogen.sh'.
I'd like to object to that name. :)
I o
Simon Josefsson wrote:
> > The first phase is a script 'autopull.sh'.
> > The second phase is a script 'autogen.sh'.
> ...
> > The names of these scripts end with '.sh' in order to make them easily
> > editable in editors that recognize the file type from the suffix.
>
> What do you think about dr
Simon Josefsson wrote:
> Thinking about all this, do we really need two new scripts? There
> is inflation in all these tools and documentation files. Could the
> separation be done via './bootstrap --pull' and './bootstrap --generate'
> with the default './bootstrap' be to do both?
It's two diff
Bruno Haible writes:
> Recent discussion in gnu-prog-discuss has shown that making the separation
> into two phases (1) and (2) explicit will have several benefits:
Wonderful, thank you! I have yet to digest everything, so I'll fall
back on stylistic comments:
> The first phase is a script 'au
Hi Paul,
> Unfortunately that didn't work for me when I tried it with GNU Tar,
> which led to some of my confusion.
>
> Here's how I can reproduce the problem, starting with a fresh checkout
> of the latest GNU Tar (commit 5c4f8cadbd362497dc3c3136566589557ce00f1b).
> The following commands rep
On 7/24/22 16:18, Bruno Haible wrote:
For (a), everything works already. The old 'bootstrap' script has
hardwired code to fetch gnulib/build-aux/bootstrap. This gets executed,
and this intermediate, not really functional 'bootstrap' script gets
copied into the package and gets executed. It notic
Replying to https://lists.gnu.org/archive/html/bug-gnulib/2022-07/msg00058.html
:
Hi Paul,
> I got confused by the two Gnulib files build-aux/bootstrap and top/bootstrap.
> Although top/bootstrap says "The canonical version of this script is
> maintained as build-aux/bootstrap in gnulib", it's
On 7/24/22 09:09, Bruno Haible wrote:
For GNU tar some adjustment of the bootstrap.conf is needed.
Thanks, I attempted to do that by installing the attached patch into GNU
'tar'.
I got confused by the two Gnulib files build-aux/bootstrap and
top/bootstrap. Although top/bootstrap says "The
Hi dear GNU libidn developers (Simon et al.),
The 'bootstrap' script from Gnulib has been reorganized to work in two phases:
(1) Fetch auxiliary files that are not in the git checkout.
This is the part that requires network access and that has
supply-chain concerns.
(2) Generate fi
Hi dear GNU poke developers (José et al.),
The 'bootstrap' script from Gnulib has been reorganized to work in two phases:
(1) Fetch auxiliary files that are not in the git checkout.
This is the part that requires network access and that has
supply-chain concerns.
(2) Generate files
Hi dear GNU wget developers (Tim et al.),
The 'bootstrap' script from Gnulib has been reorganized to work in two phases:
(1) Fetch auxiliary files that are not in the git checkout.
This is the part that requires network access and that has
supply-chain concerns.
(2) Generate files
Hi dear GNU tar developers (Sergey et al.),
The 'bootstrap' script from Gnulib has been reorganized to work in two phases:
(1) Fetch auxiliary files that are not in the git checkout.
This is the part that requires network access and that has
supply-chain concerns.
(2) Generate file
Hi all 'bootstrap' users,
Over the last few years, it has become more and more clear that bootstrap
does two things:
(1) Fetch auxiliary files that are not in the git checkout.
This is the part that requires network access and that has
supply-chain concerns.
(2) Generate files such
20 matches
Mail list logo
