public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dane Smith <c1pher@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] EAPI bump should require revbump
Date: Fri, 19 Oct 2012 10:54:30 -0400	[thread overview]
Message-ID: <508169A6.3020608@gentoo.org> (raw)
In-Reply-To: <50815B0B.7060705@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 10/19/12 09:52, 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 ?
> 
> 

- From where I sit, it just makes sense to revbump if you're changing
the EAPI. However, past experience tells me it often makes sense to
make things explicit. I don't like the idea of having tons and tons of
policies, but sometimes it helps if things are clear rather than implied.

- -- 
Dane Smith (c1pher)
Gentoo Linux Developer -- QA / Crypto
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJQgWmlAAoJEEPsD3/icQSzygkQAJYHr3UpRObSRP3C0GuGN4yK
tfDTfyv3zVtZ59eENlXEKEriS1uP9PCVTUJSs4nSeZb7DeEndj/CVoG2xqQrBKY9
+7oWLK+4jqmgAsgpiLmBq3ME7VEnwbjcb4eUM7L4q8zjWBHL+RJbPxWPIL7kMv2K
MbztJllSesiCXjFH/kTmS7SeR6EXXdKLuNGOQo6yfQGO3sixCGDziE04PzzZpqwl
2DiMSv6uPbC/Wf0cWueh6JO0rDKIm6X4ZubJbwQ6NHBvuMCg8VFElj0v3wECiqdx
TiSjv4e0xFYO7hyVfXmTJ+boPRD9X9THnvCLZfYnMBAhjwNhTCSHkeiFIXCHfb6c
WOqVVHaDmbaB2osA72hCbQjC9Ys6JHhTOvulvX2Fv3JYOG8UnNsAJT3S/Ea/l0hB
f/WRcMtAyFtviEexvGNXkrx0K9AnfNox07fJQo9HQbZ7QDa7AtqT2jwQvBQeWcf/
o5818Extw3z6MiWKQ/JhL3A6pmgKgPbCRXXXAjlSNxTaEIFcfelQZdhmlxQiHdqY
h5VUGOnMjyLtBo0pjPz+2zXOMaOuX1kZeIowRsOAy7yGqVXQ1HLi81hlzMa7IlMF
A4l3YyAfSJrYszEQKSmBJlBUVkA+4/K5cdDo/ZH/bMGNq9Ry+sNOQMaq6Jqwr8Iu
A4RO74+QsPLd2KRV3LuK
=9gKs
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2012-10-19 15: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 [this message]
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
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=508169A6.3020608@gentoo.org \
    --to=c1pher@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