Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-python
Navigation:
Lists: gentoo-python: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-python@g.o
From: Dirkjan Ochtman <djc@g.o>
Subject: Adding new packages
Date: Thu, 21 Jun 2012 13:47:31 +0200
I was wondering: what do you all think about putting new python
packages in the tree?

The idea here is IMO we shouldn't add more packages to the tree than
we can manage. We have a pretty big open bug list and enough version
bumps to go around as it is. If we move packages into the tree just
because a single user asked for it, I worry it might not be a good
trade-off: we're more or less committed to maintaining it forever, and
we do this at the cost of maintenance for other packages.

Maybe the answer is I just shouldn't worry so much, or maybe we should
try have some informal criteria for when we allow a package to go into
the tree? For instance, if one of the python devs is using a package
himself, I have no qualm about letting him add it to the tree, since
he'll probably also be able to do some maintenance. If there are 10
guys asking for it in Bugzilla, we should also include it. If we have
something in the tree already that starts depending on it, that also
probably is good enough (although this may not be always true, for
optional dependencies). But for the other cases, should we be
conservative about adding packages or just add away whenever we feel
like it?

Cheers,

Dirkjan


Navigation:
Lists: gentoo-python: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
New eclass: obsoleting old python versions
Next by thread:
pypy
Previous by date:
Re: New eclass: obsoleting old python versions
Next by date:
pypy


Updated Jun 29, 2012

Summary: Archive of the gentoo-python mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.