Re: Nominations for Anthropic’s Claude for Open Source program

[Carlos O'Donell via Gdb <gdb@sourceware.org>]

On 6/16/26 10:59 AM, Adhemerval Zanella Netto wrote:
> 
> 
> On 16/06/26 11:50, Xi Ruoyao wrote:
>> On Mon, 2026-06-15 at 20:10 -0300, Adhemerval Zanella Netto wrote:
>>> 6. Internal script cleanup
>>>
>>> This might be a more contentious one, but I think we can reduce our build
>>> dependencies by at least rewriting the Perl script to either awk or Python.
>>
>> Hmm, it seems glibc can already build w/o Perl (if you don't care the
>> info pages which need Texinfo).  I happened to figure that out after
>> forgetting the temporary Perl and Texinfo installations before building
>> glibc when I performed a test build of Linux From Scratch manually
>> several days ago.
> 
> We still install the mtrace, so to use all the glibc features one would
> need to install perl. The scripts/test-installation.pl is already gated
> through perl existence, but I think it is not a good design if we silent
> disable testing due missing tools.

(1) Dependencies.

May we please start a new there for this?

Particularly around "build", "test", and "runtime" dependencies.
  
>>
>> Also reducing the Perl scripts won't help too much for distros as
>> Texinfo is still in Perl and the distros will need the info pages
>> anyway.
>>
> 
> I think the main gain is for mtrace, the two other scripts
> (test-installation.pl, summary.pl) are not essential.  The summary.pl is
> only required for manual generation and you put texinfo already brings it
> anyway.
> 

(2) Bootstrap.

May we please start a new thread for this?

This is another distinct discussion which has to do with reducing
toolchain bootstrap dependencies. I say "bootstrap" because you should
have a way to bootstrap (to do reproducible builds, or audit a minimal
bootstrap seed, or bringup hardware) that needs the fewest number of
things you can manage. This can include disabling features during the
bootstrap.

-- 
Cheers,
Carlos.