From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] The order of functions for upgrade/downgrade
Date: Sun, 04 Apr 2010 00:22:11 +0300 [thread overview]
Message-ID: <4BB7B183.3060005@gentoo.org> (raw)
In-Reply-To: <201004032219.50735.levertond@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
On 04/04/2010 12:19 AM, David Leverton wrote:
> On Saturday 03 April 2010 22:11:55 Petteri Räty wrote:
>> What is the order that other PMs currently use?
>
> Paludis uses the "old" order for EAPIs 0 and 1, and the "new" order for 2 and
> 3 (going by the EAPI of the newly-installed package). I thought the plan was
> for PMS to specify the new order for 2 and later (and in practice, probably
> make it undefined for 0 and 1) so it's probably an oversight that it doesn't.
>
Yeah this seems prudent to me and was actually what we were just talking
about on #gentoo-dev.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
prev parent reply other threads:[~2010-04-03 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 21:11 [gentoo-pms] The order of functions for upgrade/downgrade Petteri Räty
2010-04-03 21:19 ` David Leverton
2010-04-03 21:22 ` Petteri Räty [this message]
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=4BB7B183.3060005@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-pms@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