From: "Nikolaj Sjujskij" <sterkrig@myopera.com>
To: gentoo-python@lists.gentoo.org
Cc: "Krzysztof Pawlik" <nelchael@gentoo.org>
Subject: Re: [gentoo-python] New eclass for Python
Date: Sat, 12 May 2012 13:19:06 +0400 [thread overview]
Message-ID: <op.wd6ut4ruh7emz2@verkdatorn.npdb> (raw)
In-Reply-To: <4F4D4380.9070909@gentoo.org>
Den 2012-02-29 01:13:36 skrev Krzysztof Pawlik <nelchael@gentoo.org>:
> Hello,
>
> After some work during weekend on Python packages I've decided to start a
> rewrite of Python/distutils eclass for installing Python packages.
> ...
> Highlights:
> ...
> - uses PYTHON_TARGETS use-expand (no more python-updater, whoooo!)
Hm... Does it require users to maintain correct PYTHON_TARGETS in
make.conf? No default/fallback value? app-admin/eclean-kernel has just
switched to new eclass and...
!!! The ebuild selected to satisfy "app-admin/eclean-kernel" has unmet
requirements.
- app-admin/eclean-kernel-0.3::gentoo USE="(multilib)"
PYTHON_TARGETS="-python2_6 -python2_7"
The following REQUIRED_USE flag constraints are unsatisfied:
any-of ( python_targets_python2_6 python_targets_python2_7 )
It's not big deal, of course, but kind of annoying after so many years of
automatic "build for current Python version unless USE_PYTHON is set".
next prev parent reply other threads:[~2012-05-12 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 21:13 [gentoo-python] New eclass for Python Krzysztof Pawlik
2012-02-29 5:13 ` Mike Gilbert
2012-02-29 8:11 ` Dirkjan Ochtman
2012-03-03 7:59 ` Arfrever Frehtes Taifersar Arahesis
2012-03-25 18:56 ` [gentoo-python] Re: [gentoo-dev] " Krzysztof Pawlik
2012-05-12 9:19 ` Nikolaj Sjujskij [this message]
2012-05-12 10:04 ` [gentoo-python] " Krzysztof Pawlik
2012-05-12 17:20 ` Michał Górny
2012-05-12 20:32 ` Mike Gilbert
2012-05-13 19:57 ` Dirkjan Ochtman
2012-05-14 16:12 ` Krzysztof Pawlik
2012-05-14 17:42 ` Nikolaj Sjujskij
2012-05-14 18:00 ` Krzysztof Pawlik
2012-05-13 6:55 ` Nikolaj Sjujskij
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=op.wd6ut4ruh7emz2@verkdatorn.npdb \
--to=sterkrig@myopera.com \
--cc=gentoo-python@lists.gentoo.org \
--cc=nelchael@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