Karl Berry <[email protected]> writes:
> If you want to ensure you have the current versions of texinfo.tex,
> config.{guess,sub}, and so on, yes, you should get them from gnulib (or
> other upstreams, but we copy them into gnulib precisely to make it
> simpler for people to get the current versions).
>
> gnulib is what we (I) keep up to date with upstream changes, typically
> within a day or two.
>
> What I do for some of my projects where I don't have or want a whole
> gnulib checkout hanging around is extract the build-aux directory from
> its repository into a local directory (/home/ftp/dist in the code
> below):
>
> # git incantation from Ben Pfaff, bug-gnulib 17 Jan 2012 18:38:18.
> auxtar=/tmp/build-aux.tar.gz
> if git archive --remote=git.sv.gnu.org:/srv/git/gnulib.git \
> refs/heads/master build-aux | gzip >$auxtar-new; then
> (
> cd /home/ftp/dist || exit 1
> mv $auxtar $auxtar-old
> mv $auxtar-new $auxtar || exit 1
> rm -rf build-aux
> tar xf $auxtar
> )
> fi
>
> It would be possible to use the srclist-update script and srclist.txt
> files (in gnulib/config, which is tiny, and rarely changes) to update
> from there. I do that sometimes.
>
> Another approach I've used in other cases is to compare the desired
> build-aux files in a script run from cron, like the below. There are
> some special cases in there that we need in TeX Live but I hope the idea
> is clear enough.
>
> No doubt other people have taken other approaches.
An easier way, if you only require a few files and/or cannot remember
that git invocation is to fetch them using wget or curl.
For example, to get texinfo.tex you would use one of the following:
https://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/texinfo.tex
https://raw.githubusercontent.com/coreutils/gnulib/refs/heads/master/build-aux/texinfo.tex
The GitHub one is likely much faster and will have less downtime. It is
maintained by Coreutils and Gnulib committers.
Collin
