From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] xdg.eclass: add EAPI 8 support
Date: Thu, 15 Jul 2021 09:29:46 -0400 [thread overview]
Message-ID: <YPA4SoIzNTXXRAdL@eversor> (raw)
In-Reply-To: <u35sflnif@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On Thu, Jul 15, 2021 at 03:23:04PM +0200, Ulrich Mueller wrote:
> >>>>> On Thu, 15 Jul 2021, Ionen Wolkens wrote:
>
> > Old DEPEND should be kept as-is not to risk breaking packages with odd
> > checks that need it present at build time. I'd rather no RDEPEND switch
> > either as it'll just complicate things with revbumps and tools don't
> > really need to be in RDEPEND given the above.
>
> Well, if the challenge was to pick the _worst_ match out of
> {,B,R,I}DEPEND then DEPEND would be the correct answer. :)
Well, if really must improve it, I think BDEPEND is the better choice.
Some packages use desktop-file-validate for their tests and the like.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-15 13:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 11:19 [gentoo-dev] [PATCH] xdg.eclass: add EAPI 8 support Florian Schmaus
2021-07-15 12:03 ` Ulrich Mueller
2021-07-15 13:22 ` Mart Raudsepp
2021-07-15 13:00 ` Ionen Wolkens
2021-07-15 13:23 ` Ulrich Mueller
2021-07-15 13:29 ` Ionen Wolkens [this message]
2021-07-15 18:17 ` Mike Gilbert
2021-07-21 15:08 ` [gentoo-dev] [PATCH v2] " Florian Schmaus
2021-07-21 16:37 ` Ulrich Mueller
2021-08-03 11:40 ` Mart Raudsepp
2021-08-09 18:32 ` [gentoo-dev] [PATCH v3 1/2] " Florian Schmaus
2021-08-09 18:32 ` [gentoo-dev] [PATCH v3 2/2] xdg.eclass: drop support for EAPI 4 Florian Schmaus
2021-08-10 18:21 ` Andreas Sturmlechner
2021-08-10 8:31 ` [gentoo-dev] [PATCH v3 1/2] xdg.eclass: add EAPI 8 support Andreas Sturmlechner
2021-08-11 11:54 ` Florian Schmaus
2021-08-11 12:40 ` Andreas Sturmlechner
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=YPA4SoIzNTXXRAdL@eversor \
--to=ionen@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