From: Nekun <nekokun@firemail.cc>
To: Zac Medico <zmedico@gentoo.org>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Implement new userpatch feature in existing eclass?
Date: Thu, 08 Apr 2021 13:37:00 +0000 [thread overview]
Message-ID: <fcbaea72da3c7cfe3029f84bd2ab4622@firemail.cc> (raw)
In-Reply-To: <6a1c4194-0526-96ea-d517-1c902431d439@gentoo.org>
On 2021-04-04 20:49, Zac Medico wrote:
>
> Today, I count only 2445, or 8.3% of ebuilds have EAPI 5.
>
> I imagine that the migration is moving along, since we deprecated EAPI
> 5
> on 2020-11-26 here:
>
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b2e281bb698eb93704e1987dc4df1cf2dd3c2cff
Thanks for the reply.
Also, I found that all functions which perform portageq calls should be
pass-able to ebuild-ipc daemon and all that existing functions is a
members of EAPI, declared in bin/eapi.sh. Should I add my portageq
wrapper called from eapply_user to EAPI? In the other side, this wrapper
is not intended to be called directly from ebuilds...
prev parent reply other threads:[~2021-04-08 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 17:54 [gentoo-portage-dev] Implement new userpatch feature in existing eclass? Nekun
2021-04-04 20:48 ` Zac Medico
2021-04-04 20:49 ` Zac Medico
2021-04-08 13:37 ` Nekun [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=fcbaea72da3c7cfe3029f84bd2ab4622@firemail.cc \
--to=nekokun@firemail.cc \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=zmedico@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