From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: base-system@gentoo.org, mgorny@gentoo.org, Sam James <sam@gentoo.org>
Subject: [gentoo-dev] [PATCH 0/2] unpacker.eclass: avoid duplicate unpacker_src_uri_depends deps
Date: Mon, 16 Jan 2023 17:43:25 +0000 [thread overview]
Message-ID: <20230116174327.3926794-1-sam@gentoo.org> (raw)
I've diffed metadata before/after and everything looks as expected. The only
notable cases really were games-arcade/rocksndiamonds, games-arcade/rocksndiamonds,
sys-apps/ed, sys-fs/bcachefs-tools and only sys-apps/ed had a problematic || ( ...)
dep, apparently, because of its SRC_URI (verify-sig + mirror listed).
Sam James (2):
unpacker.eclass: flatten unpacker_src_uri_depends dependencies
sys-apps/ed: use unpacker_src_uri_depends again
eclass/unpacker.eclass | 29 ++++++++++++++---------------
sys-apps/ed/ed-1.19-r1.ebuild | 7 +------
2 files changed, 15 insertions(+), 21 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-16 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 17:43 Sam James [this message]
2023-01-16 17:43 ` [gentoo-dev] [PATCH 1/2] unpacker.eclass: flatten unpacker_src_uri_depends dependencies Sam James
2023-01-16 17:43 ` [gentoo-dev] [PATCH 2/2] sys-apps/ed: use unpacker_src_uri_depends again Sam James
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=20230116174327.3926794-1-sam@gentoo.org \
--to=sam@gentoo.org \
--cc=base-system@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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