public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] EAPI bump should require revbump
Date: Sat, 20 Oct 2012 13:14:22 +0300	[thread overview]
Message-ID: <5082797E.5090803@gentoo.org> (raw)
In-Reply-To: <20610.31099.278955.288479@a1i15.kph.uni-mainz.de>

On 20/10/12 13:14, Ulrich Mueller wrote:
>>>>>> On Fri, 19 Oct 2012, Ian Stakenvicius wrote:
>
>> Hey all -- there was just a discussion in #gentoo-dev about this, so
>> following up here..
>
>> Due to the fact that an EAPI-bump can imply different behaviour from
>> eclasses or the PM, an EAPI-bump should in most cases also require an
>> ebuild revbump.
>
>> Why i'm bringing this up here, is because Chansaw and I were wondering
>> if common sense will not be enough to ensure this and it should be
>> made a policy to revbump when migrating to a new EAPI ?
>
> So far the guideline was that a revbump isn't required if the files
> installed by the ebuild don't change, or if there are only trivial
> changes that don't affect functionality (like files going to
> /usr/share/doc).
>
> 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?
>
> Ulrich
>

+1.   PM's that can't handle EAPI bump without revbump are broken in my 
eyes.

If the content doesn't change, then revbumps are *annoying waste of CPU 
cycles*

- Samuli


  reply	other threads:[~2012-10-20 12:02 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 [this message]
2012-10-20 10:34     ` Agostino Sarubbo
2012-10-20 13:33     ` Pacho Ramos
2012-10-20 11:25   ` Rich Freeman
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=5082797E.5090803@gentoo.org \
    --to=ssuominen@gentoo.org \
    --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