On Sat, Dec 14, 2013 at 01:48:42AM -0500, Theodore Ts'o wrote:
> Maybe I have an overly long memory, but I remember when the FSF let
> politics intrude by making changes to config.guess to promote the
> GNU/Linux name, which had the affect of breaking packages that blindly
> trusted that you could always update config.guess.
Certainly in the last ten years I've never once seen a bug caused by
updated config.{guess,sub}, but I've seen hundreds (if not thousands, by
now) of failures caused by not doing so.
> That plus the fact that I don't trust changes to autoconf not to
> randomly cause breakage, is why I ship upstream e2fsprogs sources with
> a generated configure and shiped config.guess/config.sub that I can
> personally test to be sane.
This is of course conflating two separate issues. It's quite possible
to update config.{guess,sub} without updating autoconf.
> I've already updated the upstream e2fsprogs sources to have an updated
> version of config.guess and config.sub to support ppc64el. It will be
> in the soon-to-be-released e2fsprogs 1.42.10.
Thanks, although it's a shame that this approach means we will
inevitably continue to run into this with new ports entirely
unnecessarily.
Regards,
--
Colin Watson [cjwat...@debian.org]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
