public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Andreas Fink <finkandreas@web.de>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] sys-devel/autoconf wrong dependency?
Date: Wed, 31 Jan 2024 17:22:01 +0100	[thread overview]
Message-ID: <w6gjznpv5g6.fsf@uni-mainz.de> (raw)
In-Reply-To: <20240131135653.7b5ef23c@anfink-laptop> (Andreas Fink's message of "Wed, 31 Jan 2024 13:56:53 +0100")

>>>>> On Wed, 31 Jan 2024, Andreas Fink wrote:

> With the move of sys-devel/autoconf to dev-build/autoconf the ebuild
> has some inconsistency, namely in the RDEPEND section, it is saying:

> RDEPEND="
>         ${BDEPEND}
>> =dev-build/autoconf-wrapper-20231224
>         sys-devel/gnuconfig
>         !~sys-devel/${P}:2.5
> "

> This should probably be `!~dev-build/${P}:2.5`. [...]

No, it should be ${CATEGORY}/${P} when referring to the package itself.
That's what these variables are for.

Ulrich


      parent reply	other threads:[~2024-01-31 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 12:56 [gentoo-dev] sys-devel/autoconf wrong dependency? Andreas Fink
2024-01-31 16:15 ` Zac Medico
2024-01-31 16:22 ` 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=w6gjznpv5g6.fsf@uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=finkandreas@web.de \
    --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