From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: [gentoo-pms] The order of functions for upgrade/downgrade
Date: Sun, 04 Apr 2010 00:11:55 +0300 [thread overview]
Message-ID: <4BB7AF1B.3060203@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
http://dev.gentoo.org/~zmedico/portage/doc/ch05.html#package-ebuild-phases
Currently PMS has what <2.1.5 does.
21:05 < Betelgeuse> zmedico: We should put a note to devmanual that if
you rely on order of things you should use at least that EAPI
21:06 < zmedico> Betelgeuse: EAPI 1
21:06 < zmedico> oh, I mean EAPI 2
21:06 < zmedico> <2.1.5 supported EAPI 1
What is the order that other PMs currently use? If the new order is used
by everyone currently maybe we should change the order for EAPIs like 2
and 3. At least should have the current behavior of Portage for EAPI 4
so that if people need it then they should use EAPI 4. I know that
Portage shouldn't have changed it so no reason to bring it up.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next reply other threads:[~2010-04-03 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 21:11 Petteri Räty [this message]
2010-04-03 21:19 ` [gentoo-pms] The order of functions for upgrade/downgrade David Leverton
2010-04-03 21:22 ` 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=4BB7AF1B.3060203@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