[PATCH v2 3/3] scripts: Support custom Git URLs in build-many-glibcs.py
Joseph Myers
josmyers@redhat.com
Thu Nov 27 18:02:44 GMT 2025
On Thu, 27 Nov 2025, Carlos O'Donell wrote:
> This is a design choice.
>
> We are purposely being conservative here with the script, it has the potential
> to really impact your network/CDN/VCS if you run this in a loop and the
> default
> is to always pull from the network.
>
> It enables a use case where you use minimal network/CDN and VCS resources
> if the versions haven't changed, and you can be guaranteed you won't update
> to a new version of the tools. If a new version is added in the script then
> it will error out for you to inspect status and do an update if required.
>
> If you want to always update, the you as a user of the script can just always
> pass --replace-sources but realize this impacts the resources you're pulling
> from.
Also, if as a user you've replaced a component checkout with a different
version from a different location for testing purposes, the current
default prevents the script from wiping out whatever local changes you
might have by replacing the checkout.
--
Joseph S. Myers
josmyers@redhat.com
More information about the Libc-alpha
mailing list