public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich@thefreemanclan.net>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] EAPI bump should require revbump
Date: Sat, 20 Oct 2012 07:25:45 -0400	[thread overview]
Message-ID: <CAGfcS_nEQQuQy4RWXO4J+Kfz2tbCo1pWw6BUajCK_CUVY+iJ7Q@mail.gmail.com> (raw)
In-Reply-To: <20610.31099.278955.288479@a1i15.kph.uni-mainz.de>

On Sat, Oct 20, 2012 at 6:14 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
> I don't see why EAPI bumps should be handled differently from other
> changes to the ebuild. If the installed files don't change, why would
> one impose upon the user to recompile the package?

It would probably be best for this reason to wait until the package
actually does change to do an EAPI bump.

One thing that would concern me is testing - I don't like the idea of
stable packages changing in any way, since that bypasses the testing
cycle (both the formal cycle by the arch team, and the informal one by
being keyworded for testing for 30 days).

Also, the on-disk image really does have to not change.  An EAPI bump
might cause subtle changes that the maintainer might not be aware of.

All that said, I think you have a decent point.

Rich


  parent reply	other threads:[~2012-10-20 12:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 13:52 [gentoo-project] EAPI bump should require revbump Ian Stakenvicius
2012-10-19 14:27 ` Matthew Thode
2012-10-19 14:54 ` Dane Smith
2012-10-20 10:14 ` Ulrich Mueller
2012-10-20 10:14   ` Samuli Suominen
2012-10-20 10:34     ` Agostino Sarubbo
2012-10-20 13:33     ` Pacho Ramos
2012-10-20 11:25   ` Rich Freeman [this message]
2012-10-25 12:39     ` Petteri Räty
2012-10-20 20:51 ` Roy Bamford
2012-10-25 12:41 ` Petteri Räty
2012-10-25 13:16   ` Ian Stakenvicius
2012-10-25 19:15     ` Petteri Räty

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=CAGfcS_nEQQuQy4RWXO4J+Kfz2tbCo1pWw6BUajCK_CUVY+iJ7Q@mail.gmail.com \
    --to=rich@thefreemanclan.net \
    --cc=gentoo-project@lists.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