public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Python-3.2-related changes
Date: Sun, 07 Feb 2010 12:17:17 -0800	[thread overview]
Message-ID: <4B6F1FCD.7080409@gentoo.org> (raw)
In-Reply-To: <201002061203.11485.Arfrever@gentoo.org>

On 02/06/2010 03:03 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-02-05 17:40:00 Arfrever Frehtes Taifersar Arahesis napisał(a):
>> - Dependency on Python 2 should be set correctly. You can specify it directly in
>>   {,R}DEPEND or use PYTHON_DEPEND.
>>
>>     Example:
>>       PYTHON_DEPEND="2"
>>
>>       inherit python
> 
> It might be useful to provide another example:
> If given package requires e.g. Python >=2.6, but does not support Python 3, then you can
> set PYTHON_DEPEND="2:2.6".

I noticed that this generates a depedency like "|| (
=dev-lang/python-2.7* =dev-lang/python-2.6* )" which is very similar
to the way that QT3VERSIONS works in qt3.eclass. One thing that is
sub-optimal about these types of dependencies is that you end up
with lots of installed packages that have out-dated dependencies
when the next minor version of python is released (python-2.8 in
this case). In the case of the python dependencies, it might be more
optimal to use a version range like ">=dev-lang/python-2.6
<dev-lang/python-3".

-- 
Thanks,
Zac



  parent reply	other threads:[~2010-02-07 20:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 16:40 [gentoo-dev] Python-3.2-related changes Arfrever Frehtes Taifersar Arahesis
2010-02-06 10:23 ` Arfrever Frehtes Taifersar Arahesis
2010-02-06 16:54   ` Mark Loeser
2010-02-08 12:29     ` Arfrever Frehtes Taifersar Arahesis
2010-02-09  8:10       ` Thilo Bangert
2010-02-09 11:14         ` [gentoo-dev] " Duncan
2010-02-06 11:03 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2010-02-06 12:14   ` Brian Harring
2010-02-08 16:06     ` Arfrever Frehtes Taifersar Arahesis
2010-02-07 18:43   ` Markos Chandras
2010-02-08 12:14     ` Arfrever Frehtes Taifersar Arahesis
2010-02-07 20:17   ` Zac Medico [this message]
2010-02-08  0:20     ` Brian Harring
2010-02-08 12:11       ` Arfrever Frehtes Taifersar Arahesis
2010-03-01  3:13 ` Arfrever Frehtes Taifersar Arahesis
2010-03-01  5:13   ` Max Arnold
2010-03-01 23:06     ` 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=4B6F1FCD.7080409@gentoo.org \
    --to=zmedico@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