From: Johannes Huber <johu@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI usage
Date: Thu, 30 Aug 2012 13:35:21 +0200 [thread overview]
Message-ID: <1603578.7P9iFm0mDI@elia> (raw)
In-Reply-To: <503F477B.2050507@gentoo.org>
> Could you elaborate what the reasons FOR it are (not that I don't know
> any, but you brought it up) since this will add work for every developer
> to check a) how the behavior of the new EAPI impacts the current ebuild
> and b) how the behvaior of inherited eclasses change depending on EAPI.
My main arguement is a modern code base, my intention is not to touch the
ebuild if there is no reason. But if you are doing a version bump, bug fix etc
you working on the package anyway.
a) thats normal developer work
b) if there is a bug in the eclass for a specified EAPI you should file a bug
--
Johannes Huber (johu)
Gentoo Linux Developer / KDE Team
GPG Key ID F3CFD2BD
next prev parent reply other threads:[~2012-08-30 11:36 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 10:28 [gentoo-dev] EAPI usage Johannes Huber
2012-08-30 10:57 ` Rich Freeman
2012-08-30 11:29 ` Johannes Huber
2012-08-30 12:30 ` Rich Freeman
2012-08-30 13:04 ` Ian Stakenvicius
2012-08-30 13:14 ` Rich Freeman
2012-08-30 13:28 ` Michael Mol
2012-08-30 19:47 ` Thomas Sachau
2012-08-30 20:05 ` Michael Mol
2012-08-30 20:11 ` Ciaran McCreesh
2012-08-30 23:58 ` [gentoo-dev] " Duncan
2012-08-31 0:38 ` Rich Freeman
2012-08-31 3:33 ` Duncan
2012-08-31 14:23 ` Zac Medico
2012-08-31 14:49 ` Ciaran McCreesh
2012-09-02 0:16 ` Brian Harring
2012-08-30 13:33 ` [gentoo-dev] " Ian Stakenvicius
2012-08-30 12:37 ` Michael Mol
2012-08-30 12:58 ` Ian Stakenvicius
2012-08-30 13:04 ` Rich Freeman
2012-08-30 13:07 ` Ian Stakenvicius
2012-08-30 13:15 ` Rich Freeman
2012-08-31 9:03 ` Andreas K. Huettel
2012-08-31 9:11 ` Fabian Groffen
2012-08-31 9:27 ` Andreas K. Huettel
2012-08-31 9:33 ` Johannes Huber
2012-08-31 12:14 ` Rich Freeman
2012-09-02 13:10 ` Andreas K. Huettel
2012-09-02 13:46 ` Rich Freeman
2012-09-02 14:36 ` Michael Orlitzky
2012-09-03 6:19 ` [gentoo-dev] " Duncan
2012-09-04 21:06 ` [gentoo-dev] " Brian Harring
2012-09-05 1:03 ` Michael Orlitzky
2012-09-05 16:15 ` Mike Gilbert
2012-09-06 17:03 ` Michael Orlitzky
2012-09-06 17:15 ` Rich Freeman
2012-09-05 21:29 ` Brian Harring
2012-09-06 17:16 ` Michael Orlitzky
2012-09-06 17:59 ` Rich Freeman
2012-09-06 21:06 ` Brian Harring
2012-08-30 10:59 ` hasufell
2012-08-30 11:35 ` Johannes Huber [this message]
2012-08-30 13:27 ` Andreas K. Huettel
2012-08-30 19:44 ` Thomas Sachau
2012-08-30 21:25 ` Rich Freeman
2012-08-30 22:50 ` hasufell
[not found] <jEakh-71e-3@gated-at.bofh.it>
[not found] ` <jEaDE-7a4-9@gated-at.bofh.it>
[not found] ` <jEvoJ-5tM-7@gated-at.bofh.it>
[not found] ` <jEymC-7yq-9@gated-at.bofh.it>
2012-09-02 10:52 ` Vaeth
2012-09-02 11:13 ` Rich Freeman
2012-09-02 12:03 ` hasufell
2012-09-02 12:33 ` Rich Freeman
2012-09-02 13:23 ` Andreas K. Huettel
2012-09-02 18:04 ` Ciaran McCreesh
2012-09-02 17:54 ` Alexis Ballier
2012-09-02 19:04 ` Michał Górny
2012-09-02 18:02 ` Ciaran McCreesh
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=1603578.7P9iFm0mDI@elia \
--to=johu@gentoo.org \
--cc=gentoo-dev@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