From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: djc@gentoo.org
Subject: Re: [gentoo-dev] The Python problem
Date: Mon, 27 Jun 2011 21:31:41 +0200 [thread overview]
Message-ID: <20110627213141.7eb6036b@pomiocik.lan> (raw)
In-Reply-To: <BANLkTimYEeG-S8+PrTary2=iH6TCwr5UOA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Mon, 27 Jun 2011 14:28:34 +0200
Dirkjan Ochtman <djc@gentoo.org> wrote:
> So I know a bunch of people have already looked at it, and I'd like to
> know: what do you find better about the Ruby approach compared to the
> Python approach? Is it just the size of python.eclass, or are there a
> number of other issues?
Working targets. USE_PYTHON is junk. What python.eclass does now with
ABIs is a PITA, and requires manually providing a lot of redudant
information (namely, RESTRICT_PYTHON_ABIS).
Right now, each ebuild has to provide the same information in
PYTHON_DEPEND and RESTRICT_PYTHON_ABIS. Moreover, if an ebuild
supports, say, py3 and its dependency doesn't, the ebuild has to
restrict py3 too.
I'd like to see that fixed somehow. I'd like to set a single supported
Python version information in an ebuild, and let the dependency
resolver handle everything else.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2011-06-27 19:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 12:28 [gentoo-dev] The Python problem Dirkjan Ochtman
2011-06-27 12:56 ` Pascal J. Bourguignon
2011-06-27 12:57 ` Pascal J. Bourguignon
2011-06-27 13:08 ` Fabian Groffen
2011-06-27 13:43 ` Dirkjan Ochtman
2011-06-27 20:49 ` Mike Frysinger
2011-06-28 6:54 ` Joshua Saddler
2011-06-28 7:19 ` Dirkjan Ochtman
2011-06-28 11:48 ` Jorge Manuel B. S. Vicetto
2011-06-28 11:53 ` Dirkjan Ochtman
2011-06-27 20:57 ` Thomas Sachau
2011-06-29 12:43 ` Arfrever Frehtes Taifersar Arahesis
2011-06-27 15:53 ` Petteri Räty
2011-06-27 16:00 ` Dirkjan Ochtman
2011-06-27 20:46 ` Petteri Räty
2011-06-28 8:06 ` Dirkjan Ochtman
2011-06-28 8:15 ` [gentoo-dev] REMOVE Stelios Boulios
2011-06-27 20:52 ` [gentoo-dev] The Python problem Mike Frysinger
2011-06-27 21:01 ` Hans de Graaff
2011-06-27 18:23 ` Benedikt Böhm
2011-06-28 8:02 ` Dirkjan Ochtman
2011-06-27 19:31 ` Michał Górny [this message]
2011-06-28 8:04 ` Dirkjan Ochtman
2011-06-28 8:21 ` Michał Górny
2011-06-29 0:33 ` Jesus Rivero (Neurogeek)
2011-06-29 4:34 ` Michał Górny
2011-06-29 7:18 ` Andreas K. Huettel
2011-06-29 10:16 ` Pacho Ramos
2011-06-29 12:19 ` 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=20110627213141.7eb6036b@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=djc@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