Follow-up Comment #4, sr #110398 (project autoconf):
[comment #3 comment #3:]
> [comment #2 comment #2:]
>
> > The problem of course is that every package that uses gnulib has to
update.
>
> That's why we have a Gnulib. :-)
>
> More precisely, if you want to use the latest Autoconf you should also use
the latest Gnulib. If you don't need to use the latest Autoconf, older Gnulib
will do.
I am not the maintainer. At linuxfromscratch we show users how to build about
1000 open source packages, but we rely on the upstream source code. Most of
the time upstream releases the package so that autoconf or autoreconf is not
needed by us, but sometimes we do need them. For those cases where it is
needed, having different packages use different versions of gnulib makes
things difficult.
I will note that mozilla packages (firefox, seamonkey, thunderbird) still
require autoconf-2.13.
There is not a lot autoconf developers can do about that, but it certainly
would be easier if gnulib could be installed system wide.
I do have a workaround for coreutils, so you can close this ticket.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110398>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
