From: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] PYTHON_DEPEND - Suggested replacement for NEED_PYTHON
Date: Tue, 12 Jan 2010 15:11:14 +0100 [thread overview]
Message-ID: <201001121511.15095.Arfrever@gentoo.org> (raw)
In-Reply-To: <201001111114.11938.reavertm@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1270 bytes --]
2010-01-11 11:14:11 Maciej Mrozowski napisał(a):
> On Monday 11 of January 2010 01:25:45 Arfrever Frehtes Taifersar Arahesis
> wrote:
> > 2010-01-10 21:56:01 Fabian Groffen napisał(a):
> > > On 10-01-2010 09:29:28 +0100, 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.)
> > >
> > > Can you explain the intended use of this variable, and why normal DEPEND
> > > is not sufficient?
> >
> > PYTHON_DEPEND is intented to simplify specification of dependency on
> > Python.
> >
> > PYTHON_DEPEND="2:2.5" is shorter than:
> > DEPEND="|| ( =dev-lang/python-2.7* =dev-lang/python-2.6*
> > =dev-lang/python-2.5* )"
>
> Doesn't that accidentally mean that dev-lang/python is improperly slotted and
> all 2.x releases should be slotted with :2?
dev-lang/python is properly slotted.
--
Arfrever Frehtes Taifersar Arahesis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-01-12 14:08 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
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 [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=201001121511.15095.Arfrever@gentoo.org \
--to=arfrever@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