public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Robert Buchholz <rbu@gentoo.org>
Subject: Re: [gentoo-dev] PYTHON_DEPEND - Suggested replacement for NEED_PYTHON
Date: Tue, 12 Jan 2010 04:20:32 +0100	[thread overview]
Message-ID: <4B4BEA80.5070809@gentoo.org> (raw)
In-Reply-To: <201001110947.51052.Arfrever@gentoo.org>

On 01/11/10 09:47, Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-01-11 04:55:02 Sebastian Pipping napisał(a):
>>>>>   PYTHON_DEPEND="2:2.5:2.6"
>>>>>     Dependency on Python 2.6 or 2.5.
>>
>> The colon (':') has two different semantics here.
> 
> The colon is only separator of components, so it has the same semantic.
> Each component has strictly defined meaning.

The first ':' is a slot colon while the second one is a from-to colon. I
fail to see how that is the same semantic.

Also, in normal dependency notation the slot is suffix-like (e.g.
package:2) whereas in this syntax it's prefix-like - the opposite.
Wouldn't it be more intuitive to make suffix-like use of it?

Looking from another angle there is range syntax being used for
kernel-check already.  It looks like this:

  [linux >=2.6.16 <2.6.31]

(examples on <http://dev.gentoo.org/~asym/guide.xml>)

Maybe you could adjust that to your needs.  I'm not sure where that
syntax is defined but afair rbu should be a good contact on that subject
(Robert?).



Sebastian



  reply	other threads:[~2010-01-12  4: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 [this message]
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=4B4BEA80.5070809@gentoo.org \
    --to=sping@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rbu@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