public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-dev-announce] PSA: python-r1.eclass, python-single-r1.eclass, and REQUIRED_USE
Date: Mon, 27 May 2013 21:51:31 +0200	[thread overview]
Message-ID: <1369684291.21170.4.camel@localhost> (raw)
In-Reply-To: <51A37D3D.3070808@gentoo.org>

El lun, 27-05-2013 a las 11:35 -0400, Jonathan Callen escribió:
> A quick reminder for anyone using python-r1.eclass or
> python-single-r1.eclass:
> 
> These eclasses provide a ${PYTHON_REQUIRED_USE} variable that should
> be included in REQUIRED_USE under the same USE conditionals (if any)
> that ${PYTHON_DEPS} is included in DEPEND/RDEPEND.
> 
> For example, if your ebuild has:
> 
> RDEPEND="
>     python? ( ${PYTHON_DEPS}
> "
> 
> then you should also have:
> 
> REQUIRED_USE="
>     python? ( ${PYTHON_REQUIRED_USE} )
> "
> 
> And if your ebuild just has:
> 
> RDEPEND="${PYTHON_DEPS}"
> 
> then you should also have:
> 
> REQUIRED_USE="${PYTHON_REQUIRED_USE}"
> 
> Failure to include these in REQUIRED_USE may cause the eclass to die
> very late in the build process.
> 
> Thank you,
> 
> Jonathan Callen

Couldn't a repoman check be added for warning when an ebuild using that
eclasses don't set REQUIRED_USE at all?



  parent reply	other threads:[~2013-05-27 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 15:35 [gentoo-dev] PSA: python-r1.eclass, python-single-r1.eclass, and REQUIRED_USE Jonathan Callen
2013-05-27 16:23 ` Mike Gilbert
2013-05-27 17:24 ` Tomáš Chvátal
2013-05-27 21:38   ` [gentoo-dev] " Jonathan Callen
2013-05-27 19:51 ` Pacho Ramos [this message]
2013-05-29 14:51 ` Michael Palimaka
2013-05-29 15:06   ` hasufell
2013-05-29 15:16     ` Michael Palimaka
2013-05-31  6:43   ` Sergey Popov

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=1369684291.21170.4.camel@localhost \
    --to=pacho@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