Re: Upload of new Python extension packages
- To: debian-python@lists.debian.org
- Subject: Re: Upload of new Python extension packages
- From: Josselin Mouette <joss@debian.org>
- Date: Fri, 01 Jul 2005 13:11:02 +0200
- Message-id: <[🔎] 1120216262.504.5.camel@silicium.ccc.cea.fr>
- In-reply-to: <1120180827.25576.212.camel@warna.corp.google.com>
- References: <42C44884.6000807@gmx.net> <1120166498.4834.41.camel@mirchusko.localnet> <1120175375.25576.138.camel@warna.corp.google.com> <42C48A0B.70607@gmx.net> <1120180827.25576.212.camel@warna.corp.google.com>
Le jeudi 30 juin 2005 à 18:20 -0700, Donovan Baarda a écrit :
> I suggest (a bit out of the blue, in no way yet endorsed by anyone) have
> two source packages;
>
> pythonX.Y-foo (where X.Y is really "X.Y", not "2.3") that generates the
> multiple binary packages python2.2-foo, python2.3-foo, python2.4-foo,
> etc. It should build depend on each corresponding python2.2-dev,
> python2.3-dev, python2.4-dev etc.
>
> python-foo, which generates the single dummy binary package python-foo
> with the appropriate dependencies to tie it to the current default
> python.
This is complete overkill. Which problems would it actually solve?
For most python packages, a single source and binary should be enough.
No more.
--
.''`. Josselin Mouette /\./\
: :' : josselin.mouette@ens-lyon.org
`. `' joss@debian.org
`- Debian GNU/Linux -- The power of freedom
Reply to: