Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Binutils <binutils@sourceware.org>, Doug Evans <dje@google.com>
Subject: Re: [PATCH] update automake version to 1.11.6
Date: Mon, 23 Mar 2015 12:46:00 -0000	[thread overview]
Message-ID: <20150323124600.GC5438@adacore.com> (raw)
In-Reply-To: <CAKOQZ8y8aYVM0ncJVfEYBcy1vEUaqLJ+C1un3vC51bpbr=wEfQ@mail.gmail.com>

> > i don't have a problem with requiring people to use the same exact
> version.
> > i do think that requiring them to build/install by hand is
> > unreasonable.  it's pretty rare (by design) for projects to do this
> > sort of thing (commit the generated autotools), so it's pretty rare
> > for this to be an issue, so it's pretty rare for people to be
> > required to manage this.  it's a throw back to pre-distro days when
> > people were used to building/install software themselves, and it's
> > unnecessary friction for new people to get into the development
> > process today.  death by a thousand cuts and all that.
> 
> It's only a barrier for people who need to change the configure.ac or
> Makefile.am files, which is not most developers.

Agreed.

Also, I don't think that building autoconf and automake once every
few years, and then using that to generate the files is really that
much of a barrier. In the meantime, it allows us to avoid the noise
you get when slightly different versions generate slightly different
code. I personally do verify the changes in the configure files,
for instance, and ask myself whether each hunk I see makes sense
to me or not. Seeing unrelated changes because others used a different
version makes that process a little harder (and, most of the time,
I'll just start over, and push a patch that first regenerates the
file).

-- 
Joel


  parent reply	other threads:[~2015-03-23 12:46 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
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 [this message]
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=20150323124600.GC5438@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.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