From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Changing PMS to Portage Manager Specification
Date: Wed, 16 Aug 2017 11:56:01 +0200 [thread overview]
Message-ID: <22932.5809.816983.485483@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <9a8b2756-deb9-4562-1f44-828992d4c94d@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
>>>>> On Wed, 16 Aug 2017, Marek Szuba wrote:
> On 2017-08-14 23:46, William L. Thomson Jr. wrote:
>> pkgcore - does not support EAPI 6, only experimental EAPI 5
> Side note - according to
> https://wiki.gentoo.org/wiki/Project:Package_Manager_Specification
> pkgcore has supported EAPI 6 since version 0.9.3.
Right, the information on the wiki page is taken from pkgcore's NEWS
file.
> Considering it says exactly the same for EAPI 5, this is almost
> certainly a mistake - but I'd rather confirm this here before
> changing the page.
Unfortunately, information about EAPI 4 and 5 support is not entirely
clear from the NEWS file, so one must look into the git log. Quoting
bug 326459 comment 4 [1]:
EAPI 4: pkgcore-0.6.5 (2011-06-22), which is the first version
(correctly) supporting default src_install. There's another change
for EAPI 4 in 0.7, namely removal of the AA and KV variables, but I
think this can be ignored here (also it's not in the NEWS file).
EAPI 5: pkgcore-0.9.3 (2016-05-28). NEWS says for 0.9 that it has
"Nearly complete EAPI=5 support just missing subslot rebuilds."
This was finally added in 0.9.3, "Add support for PN:slot/subslot
and slotted glob targets."
So yes, it appears that full support for EAPI 5 was added only in
pkgcore-0.9.3, which supports EAPI 6 already.
Ulrich
[1] https://bugs.gentoo.org/show_bug.cgi?id=326459#c4
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2017-08-16 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 22:05 [gentoo-dev] Changing PMS to Portage Manager Specification William L. Thomson Jr.
2017-08-01 23:19 ` Sam Jorna
2017-08-12 14:50 ` Alexander Berntsen
2017-08-12 14:55 ` Gordon Pettey
2017-08-14 21:46 ` William L. Thomson Jr.
2017-08-14 22:38 ` Gordon Pettey
2017-08-16 7:54 ` Marek Szuba
2017-08-16 9:56 ` Ulrich Mueller [this message]
2017-08-16 12:54 ` Tim Harder
2017-08-14 18:42 ` Peter Stuge
2017-08-14 19:09 ` Rich Freeman
2017-08-14 21:26 ` William L. Thomson Jr.
2017-08-14 22:20 ` Rich Freeman
2017-08-14 22:39 ` William L. Thomson Jr.
2017-08-15 6:48 ` Michał Górny
2017-08-16 20:42 ` Daniel Campbell
2017-08-14 20:42 ` William L. Thomson Jr.
2017-08-14 21:20 ` 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=22932.5809.816983.485483@a1i15.kph.uni-mainz.de \
--to=ulm@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