From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PYTHON_DEPEND - Suggested replacement for NEED_PYTHON
Date: Sun, 10 Jan 2010 19:41:55 +0100 [thread overview]
Message-ID: <4B4A1F73.7040603@gentoo.org> (raw)
In-Reply-To: <201001100930.20355.Arfrever@gentoo.org>
On 01/10/10 09:29, Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to suggest introduction of support for PYTHON_DEPEND variable, which
> would be a better replacement for NEED_PYTHON variable. NEED_PYTHON variable
> does not allow to specify that e.g. only versions of Python 2 are accepted.
> (Eventually PYTHON_DEPEND variable will have to be set only in ebuilds of packages
> not supporting installation for multiple versions of Python.)
>
> Suggested syntax:
> PYTHON_DEPEND="[USE_flag?] <X[:[Y][:[Z]]]> [X[:[Y][:[Z]]]]"
> <required_component>, [optional_component]
> X - Major version of Python ('2' or '3') or '*'.
> Y - Minimal version of Python in the form of ${major_version}.${minor_version}.
> Z - Maximal version of Python in the form of ${major_version}.${minor_version}.
> It will be probably very rarely used.
>
> Examples:
> PYTHON_DEPEND="2"
> Dependency on any version of Python 2.
>
> PYTHON_DEPEND="2:2.5"
> Dependency on Python 2.7, 2.6 or 2.5.
>
> PYTHON_DEPEND="*:2.6"
> Dependency on Python 3.2, 3.1, 3.0, 2.7 or 2.6.
>
> PYTHON_DEPEND="2:2.7 3:3.1"
> Dependency on Python 3.2, 3.1 or 2.7.
>
> PYTHON_DEPEND="2:2.5:2.6"
> Dependency on Python 2.6 or 2.5.
>
> PYTHON_DEPEND="2::2.6"
> Dependency on Python 2.6, 2.5 or 2.4.
>
> PYTHON_DEPEND="python? 2"
> Dependency on any version of Python 2 when "python" USE flag is enabled.
>
While I don't object improvements or changes on that front at all:
- How are SUPPORT_PYTHON_ABIS and RESTRICT_PYTHON_ABIS affected
by NEED_PYTHON now and by PYTHON_DEPEND in the future?
- The proposed approach doesn't look intuitive to me from a quick
view, sorry: Neither the examples nor the grammar. I didn't give
it that much time to be fair, though.
Sebastian
next prev parent reply other threads:[~2010-01-10 20:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 8:29 [gentoo-dev] PYTHON_DEPEND - Suggested replacement for NEED_PYTHON Arfrever Frehtes Taifersar Arahesis
2010-01-10 18:41 ` Sebastian Pipping [this message]
2010-01-10 21:50 ` Arfrever Frehtes Taifersar Arahesis
2010-01-11 3:55 ` Sebastian Pipping
2010-01-11 8:47 ` Arfrever Frehtes Taifersar Arahesis
2010-01-12 3:20 ` Sebastian Pipping
2010-01-10 20:56 ` Fabian Groffen
2010-01-11 0:25 ` Arfrever Frehtes Taifersar Arahesis
2010-01-11 7:50 ` Fabian Groffen
2010-01-11 8:29 ` [gentoo-dev] " Duncan
2010-01-11 10:14 ` Fabian Groffen
2010-01-12 14:16 ` Arfrever Frehtes Taifersar Arahesis
2010-01-11 9:00 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2010-01-11 11:04 ` Gilles Dartiguelongue
2010-01-12 14:07 ` Arfrever Frehtes Taifersar Arahesis
2010-01-11 10:14 ` Maciej Mrozowski
2010-01-12 14:11 ` Arfrever Frehtes Taifersar Arahesis
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=4B4A1F73.7040603@gentoo.org \
--to=sping@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