Re: Upload of new Python extension packages
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Donovan Baarda schrieb:
> On Thu, 2005-06-30 at 14:21, Josselin Mouette wrote:
>
>>Le jeudi 30 juin 2005 à 21:31 +0200, Torsten Marek a écrit :
>>
>>>right now I have a package for ElementTidy [1] in my private repository [2],
>>>which I am going to upload to Debian one day (either as a DD or via a sponsor).
>>>My question is, whether I should delay the upload till after Python 2.3 is
>>>released or just happily go on and take into account the python2.3-elementtidy
>>>package being removed in some months/weeks/years/releases?
>>>There are not too many users, and a link to my repo is in the wnpp bug,
>>>therefore people can use the package already.
>>
>>Please, don't use the python2.X-foo scheme for such a small package. You
>>only need a single python-foo package, built against the default python
>>version. It eases transitions a lot, and avoids unnecessary cluttering
>>the archive.
I think I'll wait until the transition is done, then. ElementTidy depends on
ElementTree, which is a package for multiple Python versions right now, but
could be put into /usr/lib/site-python (it's Python-only).
>
>
> And should pure-python modules go into /usr/lib/site-python, or
> /usr/lib/python2.3/site-packages?
ElementTidy contains a C extension module.
>
> The first means the package will not need fixing when we transition to
> 2.4, but the second is what is documented in the python-policy.
>
> There are still quite a few things that need fixing in the policy...
>
Is something out yet? Any ideas how to deal with these problems?
greetings
Torsten
- --
Torsten Marek <shlomme@gmx.net>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCxIoLfMVFHqJEyFgRAgc2AJ9OvsKE+HA+DQU36GCPBXSn/xSgPgCeIWBZ
MpINATejMdY3Ti/vCGc9WOM=
=Go0p
-----END PGP SIGNATURE-----
Reply to: