From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion for next bugday: Mass use deps migration
Date: Sun, 22 Feb 2009 23:58:05 +0200 [thread overview]
Message-ID: <49A1CA6D.5050707@gentoo.org> (raw)
In-Reply-To: <200902222234.25275.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Carsten Lohrke wrote:
> On Freitag, 20. Februar 2009, Petteri Räty wrote:
>> Suggestions/objections?
>
> If you mean by "mass migration" doing that more or less blindly, I do object.
> When an ebuild directly or indirectly inherits an eclass, which is EAPI 2
> enabled, like base.eclass, while another isn't, you have to expect
> side-effects. See for example media-tv/kdetv-0.8.9-r1, which features an
> empty src_prepare to prevent the attempt to apply patches twice, temporarily.
>
> So the first step is to get all eclasses EAPI 2 ready and even then I wouldn't
> rule out odd cases, so changes should happen in testing and revised ebuilds
> exclusively to assure odd cases get caught.
>
>
> Carsten
Yes of course not without testing the packages. The point here was also
that if you are maintaining something do the change yourself before the
next bug day. Even if the eclasses are not EAPI 2 ready you can work
around it in the ebuild by for example those empty functions.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-02-22 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:55 [gentoo-dev] Suggestion for next bugday: Mass use deps migration Petteri Räty
2009-02-22 21:34 ` Carsten Lohrke
2009-02-22 21:43 ` Tomáš Chvátal
2009-02-22 23:41 ` Carsten Lohrke
2009-02-22 21:58 ` Petteri Räty [this message]
2009-02-22 23:35 ` Carsten Lohrke
2009-03-07 14:14 ` 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=49A1CA6D.5050707@gentoo.org \
--to=betelgeuse@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