From: Ulrich Mueller <ulm@gentoo.org>
To: Conrad Kostecki <conikost@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] eclass/eutils.eclass: drop ltprune inherit
Date: Tue, 27 Jul 2021 10:29:40 +0200 [thread overview]
Message-ID: <u1r7k9n2j@gentoo.org> (raw)
In-Reply-To: <20210726222858.9650-1-conikost@gentoo.org> (Conrad Kostecki's message of "Tue, 27 Jul 2021 00:28:57 +0200")
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
>>>>> On Tue, 27 Jul 2021, Conrad Kostecki wrote:
> No ebuilds remaining to call directly prune_libtool_files,
> so we could drop the ltprune inherit in eutils.
I see very little benefit, because a) the indirect inherit is limited to
EAPIs 5 and 6, and b) eutils is deprecated. OTOH, there's some risk of
(silent) breakage, because one can assume that eutils is still widely
used in overlays.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
prev parent reply other threads:[~2021-07-27 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 22:28 [gentoo-dev] [PATCH 1/2] eclass/eutils.eclass: drop ltprune inherit Conrad Kostecki
2021-07-26 22:28 ` [gentoo-dev] [PATCH 2/2] eclass/gstreamer.eclass: " Conrad Kostecki
2021-07-27 8:29 ` Ulrich Mueller [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=u1r7k9n2j@gentoo.org \
--to=ulm@gentoo.org \
--cc=conikost@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