From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The Python problem
Date: Mon, 27 Jun 2011 23:46:11 +0300 [thread overview]
Message-ID: <4E08EC13.5060203@gentoo.org> (raw)
In-Reply-To: <BANLkTiny_cbm51YVx15kZJuYwvBznBgY9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On 27.06.2011 19:00, Dirkjan Ochtman wrote:
> On Mon, Jun 27, 2011 at 17:53, Petteri Räty <betelgeuse@gentoo.org> wrote:
>> I like the ruby approach for the reason that it doesn't require users to
>> run update scripts like python-updater.
>
> Sure, but if that means the developers now have to bump every package
> in the tree when a new version of Python comes out, I'm not sure
> that's the best trade-off.
>
And why can't this be handled by the eclass? If the ebuild is able to
specify it supports >=3.0 meaning it's expected that future versions
work then the eclass can make the new values available through IUSE when
new python versions are out and ebuilds don't require any changes.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2011-06-27 20:47 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 [this message]
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
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=4E08EC13.5060203@gentoo.org \
--to=betelgeuse@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