On Thu, Apr 4, 2024, at 6:50 PM, Jacob Bachmeyer wrote:
> Zack Weinberg wrote:
>> The duplicate uname -m/-r/-s/-v output is replaced with
>> diagnostics of the availability of uname and a C compiler.
>
> I would suggest keeping the duplicate uname output; config.guess is
> straightforward but lengthy and duplicating this output will help us
> detect bugs in the script, should they mangle the UNAME_* variables.
> There is a reason for those to be the very last thing the script outputs.
Hmm, OK.
>> (N.B. The Savannah URLs look a little too cgit-specific to trust
>> that they will still be good twenty years from now. Can we maybe
>> get the www.gnu.org admins to make /software/???/config.{guess,sub}
>> redirect to these URLs, just for a little extra future-proofing?)
>
> I would agree that getting some stable redirects would be nice; archaic
> versions of config.guess instruct users to update from Savannah CVS or
> the main GNU release server.
>
> Logically, the redirects would be at
> www.gnu.org/software/config/config.{guess,sub} and would point to
> Savannah cgit for now.
Yeah, those paths look good. Do you have any idea who to talk to to
make that happen? Autoconf has a CVS repo that maps to the contents
of www.gnu.org/software/autoconf, but I don't know if there's any
equivalent for config.
I'm leaving the CGIT-specific paths in my patchset until we actually have
the redirects.
zw
