From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Python 3 in Gentoo
Date: Mon, 3 Sep 2012 17:12:18 -0400 [thread overview]
Message-ID: <CAJ0EP42E5RZrT4OtjiXsD7bwU6eu6byeWNLJ2bUr=tOLCgGiyQ@mail.gmail.com> (raw)
In-Reply-To: <20120902210221.2166c1e9@pomiocik.lan>
On Sun, Sep 2, 2012 at 3:02 PM, Michał Górny <mgorny@gentoo.org> wrote:
> On Sun, 2 Sep 2012 13:54:13 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
>
>> On Sun, Sep 2, 2012 at 1:34 PM, Michał Górny <mgorny@gentoo.org>
>> wrote:
>> > On Sun, 2 Sep 2012 13:16:38 -0400
>> > Mike Gilbert <floppym@gentoo.org> wrote:
>> >
>> >> On Sun, Sep 2, 2012 at 8:21 AM, Thomas Sachau <tommy@gentoo.org>
>> >> wrote:
>> >> > Mike Gilbert schrieb:
>> >> >> On Mon, Aug 13, 2012 at 3:38 PM, Dirkjan Ochtman
>> >> >> <djc@gentoo.org> wrote:
>> >> >>> On Mon, Aug 13, 2012 at 9:07 PM, Richard Yao <ryao@gentoo.org>
>> >> >>> wrote:
>> >> >>>>> Does this seem like a viable option? Is anyone going to
>> >> >>>>> volunteer to take it from here?
>> >> >>>>
>> >> >>>> I can try to make time to make these changes this weekend if
>> >> >>>> everyone is fine with that.
>> >> >>>
>> >> >>> I think we should inform gentoo-dev first.
>> >> >>>
>> >> >>
>> >> >> Just in case someone is waiting for me to take some further
>> >> >> actions on this, please don't wait on me. I really don't have
>> >> >> the motivation to carry this plan any further.
>> >> >>
>> >> >> If someone else wants to carry the torch, I am happy to assist.
>> >> >>
>> >> >>
>> >> >
>> >> > Just to get the right summary:
>> >> >
>> >> > The plan is now to replace all dependencies in ebuilds, which
>> >> > have either "dev-lang/python" or something like
>> >> > ">=dev-lang/python-X.Y" to use "virtual/python" instead?
>> >> >
>> >>
>> >> That's right.
>> >>
>> >> > What about versioned dependencies exluding python versions still
>> >> > in the main tree like ">=dev-lang/python-2.7"?
>> >> >
>> >>
>> >> In this case the virtual would not work. Instead, it could be
>> >> replaced with this:
>> >>
>> >> || ( =dev-lang/python-2.7* =dev-lang/python-3* )
>> >>
>> >> Similarly, >=dev-lang/python-2.6 could be replaced with this:
>> >>
>> >> || ( =dev-lang/python-2.7* =dev-lang/python-2.6*
>> >> =dev-lang/python-3* )
>> >
>> > You could go with virtual/python-2.7, -2.6, -2.5 being an
>> > appropriate minimal version.
>> >
>>
>> I gave that idea some thought, but I think it would be a somewhat
>> confusing (it makes my head hurt).
>>
>> There are actually a few ways I could see a versioned virtual being
>> implemented; can you articulate exactly what each virtual version
>> would have in RDEPEND and how it would be used in other ebuilds?
>
> Well, one not-so-crazy idea is that we have:
>
> virtual -2.5, SLOT="2.5+": || ( =python-2* =python-3* )
> virtual -2.6, SLOT="2.6+": || ( python:2.7 python:2.6 =python-3* )
> virtual -2.7, SLOT="2.7+": || ( python:2.7 =python-3* )
>
> # optioanlly, I think it may be nicer than =python-3* in ebuilds
> virtual -3.1, SLOT="3.1+": =python-3*
>
> It's a bit hacky but with it, you can then do:
>
> RDEPEND="virtual/python:2.6+"
>
> which is quite self-explanatory.
>
That could work. In this case, we would need to ensure that ebuilds do
not depend on virtual/python without a slot (or version wildcard).
next prev parent reply other threads:[~2012-09-03 21:12 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 2:13 [gentoo-python] Python 3 in Gentoo Mike Gilbert
2012-07-30 2:23 ` Richard Yao
2012-07-30 5:38 ` Rafael Goncalves Martins
2012-07-30 7:36 ` Dirkjan Ochtman
2012-07-30 8:23 ` Richard Yao
2012-07-30 8:32 ` Dirkjan Ochtman
2012-07-30 9:06 ` Michał Górny
2012-07-30 9:09 ` Dirkjan Ochtman
2012-07-30 9:16 ` Michał Górny
2012-07-30 9:23 ` Dirkjan Ochtman
2012-07-30 9:50 ` Michał Górny
2012-07-30 11:56 ` Dirkjan Ochtman
2012-07-30 13:11 ` Matthew Summers
2012-07-30 13:18 ` Matthew Summers
2012-07-30 13:39 ` Nikolaj Sjujskij
2012-07-30 14:05 ` Jesus Rivero (Neurogeek)
2012-07-31 7:11 ` Nikolaj Sjujskij
2012-07-31 12:09 ` Ben de Groot
2012-07-31 12:14 ` Nikolaj Sjujskij
2012-07-31 14:40 ` Ben de Groot
2012-07-31 16:46 ` Nikolaj Sjujskij
2012-07-30 14:00 ` Jesus Rivero (Neurogeek)
2012-07-30 14:04 ` Michał Górny
2012-07-30 14:07 ` Matthew Summers
2012-07-30 14:11 ` Michał Górny
2012-07-30 15:19 ` Mike Gilbert
2012-07-30 15:22 ` Dirkjan Ochtman
2012-07-30 15:30 ` Mike Gilbert
2012-07-30 15:40 ` Dirkjan Ochtman
2012-07-30 15:56 ` Mike Gilbert
2012-07-30 16:05 ` Matthew Summers
2012-07-30 16:16 ` Mike Gilbert
2012-07-30 16:20 ` Matthew Summers
2012-07-30 16:53 ` Dirkjan Ochtman
2012-07-30 17:05 ` Mike Gilbert
2012-07-31 15:31 ` Mike Gilbert
2012-08-08 21:07 ` Mike Gilbert
2012-08-08 21:44 ` Thomas Sachau
2012-08-08 22:09 ` Jesus Rivero (Neurogeek)
2012-08-13 19:05 ` Richard Yao
2012-08-13 9:46 ` Dirkjan Ochtman
2012-08-13 19:07 ` Richard Yao
2012-08-13 19:38 ` Dirkjan Ochtman
2012-08-31 2:13 ` Mike Gilbert
2012-09-02 12:21 ` Thomas Sachau
2012-09-02 17:16 ` Mike Gilbert
2012-09-02 17:34 ` Michał Górny
2012-09-02 17:54 ` Mike Gilbert
2012-09-02 19:02 ` Michał Górny
2012-09-03 21:12 ` Mike Gilbert [this message]
2012-09-03 21:20 ` Michał Górny
2012-07-30 21:33 ` Thomas Sachau
2012-07-30 7:45 ` Michał Górny
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='CAJ0EP42E5RZrT4OtjiXsD7bwU6eu6byeWNLJ2bUr=tOLCgGiyQ@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-python@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