public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: PYTHON_DEPEND - Suggested replacement for NEED_PYTHON
Date: Mon, 11 Jan 2010 11:14:40 +0100	[thread overview]
Message-ID: <20100111101440.GB886@gentoo.org> (raw)
In-Reply-To: <pan.2010.01.11.08.29.33@cox.net>

On 11-01-2010 08:29:32 +0000, Duncan wrote:
> Fabian Groffen posted on Mon, 11 Jan 2010 08:50:30 +0100 as excerpted:
> 
> > On 11-01-2010 01:25:45 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
> >> > 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* )"
> > 
> > So if there is enough space to express the dependency with the current
> > syntax, is it worth introducing a new shorthand for it then?
> > 
> > Also for this example, why does 2:2.5 expand to 2.7, 2.6 and 2.5?  I
> > would have expected 2.0 ... 2.5.  Maybe the language isn't as intuitive
> > then as Sebastian pointed out.
> 
> Initially intuitive, perhaps not, but reasonably easy after reading the 
> explanation:
> 
> The first position is major python version, the second if present, 
> minimal version (within that major), so it can be read as =>version, the 
> third if present, maximum version (within that major), so it can be read 
> as <=.
> 
> Thus, the above "2:2.5" means major version 2, minimal version 2.5 (no 
> maximum version within that major), so 2.5+.

what's wrong with ">=2.5 && <3.0" then?


-- 
Fabian Groffen
Gentoo on a different level



  reply	other threads:[~2010-01-11 12:09 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 [this message]
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=20100111101440.GB886@gentoo.org \
    --to=grobian@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