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: Sat, 20 Oct 2012 17:17:21 +0200 [thread overview]
Message-ID: <1350746241.12879.81.camel@belkin4> (raw)
In-Reply-To: <5082B07C.2030805@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]
El sáb, 20-10-2012 a las 16:09 +0200, Thomas Sachau escribió:
[...]
> And finally, as already pointed out by Rich, you should not talk about
> any specific EAPI you like/prefer/want to be used everyhwere, but
> instead about the issue you want to solve. So just point out the issue
> and ask the maintainer to fix it. If he uses a newer EAPI, good. If he
> uses another solution, which also fixes the issue, also good. We should
> not discuss about a specific way to solve some issues, since this is the
> maintainers choice. Our goal should instead be to fix as many issues as
> possible with our limited amount of time we have for Gentoo.
>
>
Also, I see your point, the problem is:
- Do we agree we should move to packages with splitted
src_configure/prepare phases? In that case eapi >=2 should be enforced.
- Do we agree mtimes should be preserved? In that case eapi >=3 should
be pushed because all ebuilds will use that enhancement.
Regarding other issues like --disable-dependency-tracking, do you know
any way to automate a check for knowing if a package that could benefit
from it (one using autotools) could pass it or not? If such a check
could exist, then, we would be able to only move that packages to newer
eapi (or pass option manually) and that would be enough to me. The same
would occur with --disable-silent-rules.
Please take care I am not trying to get latest eapi used per se, it's
because I want to see all new packages using, for example, splitted
src_compile phases, or preserved mtimes, or
--disable-dependency-tracking being passed on packages that could use
it. I thought the easiest way to do that automatically would be to try
to always use latest eapi and, then, that packages would be fixed
progressively. On the other hand, if you think the other way would be
easier, fine, but I wasn't sure how to, for example, check for the
--disable-dependency-tracking problem, or check that every package
needing revdep-rebuild will be moved to eapi5...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-10-20 15:18 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
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 [this message]
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=1350746241.12879.81.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