From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: PSA: python-r1.eclass, python-single-r1.eclass, and REQUIRED_USE
Date: Thu, 30 May 2013 00:51:23 +1000 [thread overview]
Message-ID: <ko54l7$n1b$1@ger.gmane.org> (raw)
In-Reply-To: <51A37D3D.3070808@gentoo.org>
On 28/05/2013 01:35, Jonathan Callen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> 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
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCgAGBQJRo309AAoJELHSF2kinlg4dVcP/2t3v1t8CId8jK/c4VG8HLWL
> zTEvTI3d8wQILuHydI9VkOZllo3dPWhhUhg/1qJjwEXXnKQXiYNUiVzbtwdkGro/
> OlkCrrpDstHgawHiovIZjgyEG9Y+Nz2Z5nKorZIAMFSFepaFsIkihVR3VkeHiG9Q
> 7XOOVaH8mqGuj7JWZNqikCmB11a6t08jVM68tzwtTZUuil1IRE2qjO5akMPczsvk
> 3ndoMsv5hQwUE4wmmTH4ffiz+wp/JUylK2Ypy6p/UWlMw+oq8IusyvQdKztF2rU4
> SyjnEOHcPtbLXMA24NHSAUov5L3xVcSu4he5A+QnY0Ghn0dZ7Wbk72aRZQP+MOk+
> e18tdPRaXE35ux8s0ogLeuD04lju6z5/esJbP8LF8H6loiKCURxVOfYEhUugIMIc
> ihb6h4o4cflz2tYV6USOHxUQ6pA78X7ftXGJhOOR1sf1/2GZcg7ZQvD0WqjNLbAo
> U52yQl3/bKMVpezYLhkLxgzmRAdwbBdBFdiav8dX+QNYabLPG/0y6mkqK0pc59sS
> Lsse/dXCPrxfI6MVbsSQAaFt4s/YNrf9NLabdPHShRlWX8pRc16feQFb7FoTCmWe
> BzwBwG63Mvw2OOS0GrXIfXdFs9klbezoZ8Ql8Zb3CIZPWaBPAOYfCqZDHkDDAyQL
> UYQyPJdIntHmxKbtMQr9
> =frSU
> -----END PGP SIGNATURE-----
>
>
Would it be possible to add repoman checks for this, and other common
failures like missing PYTHON_USEDEP?
next prev parent reply other threads:[~2013-05-29 14:52 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 ` [gentoo-dev] Re: [gentoo-dev-announce] " Pacho Ramos
2013-05-29 14:51 ` Michael Palimaka [this message]
2013-05-29 15:06 ` [gentoo-dev] " 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='ko54l7$n1b$1@ger.gmane.org' \
--to=kensington@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