From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Drop EAPI=0 requirement for system packages.
Date: Fri, 19 Oct 2012 20:09:15 +0200 [thread overview]
Message-ID: <1350670155.12879.22.camel@belkin4> (raw)
In-Reply-To: <20121019145105.4927316b@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
El vie, 19-10-2012 a las 14:51 -0300, Alexis Ballier escribió:
> On Fri, 19 Oct 2012 19:21:52 +0200
> Pacho Ramos <pacho@gentoo.org> wrote:
>
> [...]
>
> > What I am trying to say is that, if we agree latest eapi is
> > technically better, we need to try to get it used when possible (I
> > mean, when, for example, eclasses are ported) for a "QA" reasoning.
>
> i think we all agree that there are improvements in newer eapis.
>
> what about filling bugs, preferably with patches, when such
> improvements are really needed ? like what was done for nuking
> built_with_use.
>
> arguing to death if 'should use latest eapi' should become 'must use
> latest eapi' will never get things done :)
>
>
Because it will add even more work, I mean:
- I catch a package using and old eapi and, then, still not passing
--disable-silent-rules option. => First problem, I need to notice that
package, there are packages I simply won't notice because I don't merge
them ever or, simply, I don't notice that option is not being used.
- I need to report a bug per each package using old eapi => I would need
to report a ton of bugs for bumping eapi that, probably, I could have
directly bumped myself if I would be allowed to (I already do it in my
maintained packages and maintainer-needed ones, but not for others as
maybe their maintainers dislike...)
- Maintainer need to check that bug and commit the change or reject the
bump (in that case we would be blocked if maintainer doesn't bump it for
some strange reason). There are also some devs really slow to reply.
- This effort needs to be done again and again in the future with newer
eapis, while could be "automatically" done on next bump by maintainer.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-10-19 18:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 10:53 [gentoo-dev] [RFC] Drop EAPI=0 requirement for system packages Ralph Sennhauser
2012-10-12 20:38 ` Walter Dnes
2012-10-12 20:41 ` Ciaran McCreesh
2012-10-12 20:45 ` Ian Stakenvicius
2012-10-12 21:02 ` Alexandre Rostovtsev
2012-10-13 3:10 ` [gentoo-dev] " Ryan Hill
2012-10-13 6:28 ` Ralph Sennhauser
2012-10-17 5:42 ` Ryan Hill
2012-10-17 17:34 ` Pacho Ramos
2012-10-17 19:00 ` Rich Freeman
2012-10-18 4:07 ` Ryan Hill
2012-10-18 13:36 ` Rich Freeman
2012-10-18 15:49 ` Pacho Ramos
2012-10-18 17:49 ` Rich Freeman
2012-10-18 19:05 ` Pacho Ramos
2012-10-18 19:35 ` Rich Freeman
2012-10-19 17:21 ` Pacho Ramos
2012-10-19 17:51 ` Alexis Ballier
2012-10-19 18:09 ` Pacho Ramos [this message]
2012-10-19 18:47 ` Alexis Ballier
2012-10-19 19:32 ` Pacho Ramos
2012-10-19 19:43 ` Thomas Sachau
2012-10-19 19:53 ` Pacho Ramos
2012-10-19 20:39 ` Thomas Sachau
2012-10-19 20:47 ` Rich Freeman
2012-10-20 6:04 ` Pacho Ramos
2012-10-20 14:09 ` Thomas Sachau
2012-10-20 14:29 ` Pacho Ramos
2012-10-20 14:53 ` Pacho Ramos
2012-10-20 15:15 ` Thomas Sachau
2012-10-20 15:19 ` Pacho Ramos
2012-10-20 15:17 ` Pacho Ramos
2012-10-20 15:57 ` Thomas Sachau
2012-10-20 15:24 ` Rich Freeman
2012-10-19 20:43 ` Alexis Ballier
2012-10-20 6:07 ` Pacho Ramos
2012-10-20 6:14 ` Michał Górny
2012-10-20 6:31 ` Pacho Ramos
2012-10-20 14:37 ` Peter Stuge
2012-10-19 4:09 ` Ryan Hill
2012-10-19 4:34 ` Zac Medico
2013-04-12 16:25 ` [gentoo-dev] Binary package dependencies for sub-slot-less EAPIs W. Trevor King
2013-04-12 18:38 ` Rich Freeman
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=1350670155.12879.22.camel@belkin4 \
--to=pacho@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