Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] update automake version to 1.11.6
Date: Thu, 19 Mar 2015 12:06:00 -0000	[thread overview]
Message-ID: <20150319120631.GB4884@adacore.com> (raw)
In-Reply-To: <1426310999-13103-1-git-send-email-vapier@gentoo.org>

> Debian stable (wheezy) and newer only have 1.11.6.
> Ubuntu Trusty and newer only have 1.11.6.
> Gentoo dropped <=1.11.5 2 years ago.
> Fedora R17 was the last one to offer 1.11.x (it was 1.11.6).
> Centos 7 doesn't offer any 1.11.x version.
> OpenSUSE 12.2 was the last one to offer 1.11.x.
> Arch Linux dropped 1.11.x 3 years ago.
> Mageia 2 was the last one to offer 1.11.x.
> 
> So anyone who readily has access to automake 1.11.[0-5] is using a two
> year old distro that is no longer supported.  Lets use 1.11.6 as it's
> the only 1.11.x version that is easily available.
> 
> 2015-03-14  Mike Frysinger  <vapier@gentoo.org>
> 
> 	* README-maintainer-mode: Update automake to 1.11.6.

FWIW, I tend to avoid using the auto-tools already installed, because
I don't know what patches they might contain. Those patches can result
in small differences which inexplicably show up when you regenerate
some files after making some modifications. That's why I rebuilt
them all from source, and use them when regenerating files.

All in all, I'm not against switching to 1.11.6 but we should then
regenerate all affected files now, and I would prefer it if that was
done using an unmodified release rather than one that might have been
modified by the distro.

-- 
Joel


  reply	other threads:[~2015-03-19 12:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150311094134.GE9455@vapier>
2015-03-14  5:30 ` Mike Frysinger
2015-03-19 12:06   ` Joel Brobecker [this message]
2015-03-19 22:59     ` Doug Evans
2015-03-19 23:04       ` Mike Frysinger
2015-03-20 23:58         ` Doug Evans
2015-03-21 19:59           ` Mike Frysinger
2015-03-21 21:29             ` Doug Evans
     [not found]             ` <CAKOQZ8y8aYVM0ncJVfEYBcy1vEUaqLJ+C1un3vC51bpbr=wEfQ@mail.gmail.com>
2015-03-23 12:46               ` Joel Brobecker
2015-03-23 12:57                 ` H.J. Lu
2015-03-23 13:13                   ` Joel Brobecker
2015-03-23 23:46                   ` Alan Modra
2015-03-24  6:16                     ` Mike Frysinger
2015-03-24 17:02                     ` Joseph Myers
2015-03-23 20:21                 ` Cary Coutant
2015-03-23 20:29                   ` H.J. Lu
2015-03-24  6:15                 ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150319120631.GB4884@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox