Sebastian Reichel wrote: > On Tue, Mar 03, 2009 at 06:20:33PM +0100, Emilio Pozuelo Monfort wrote: >> Really? Where is that package? I can't find it. > > I found it @ http://python-modules.alioth.debian.org/cgi-bin/pet.cgi > under "Ready for upload" section. Seems it's hidden there since > 1 > year :) Ah, it has never been uploaded to the archive, and the ITP was 'timed out'. >>> Now for my questions: >>> - Which one should be renamed? My suggestion is to rename your >>> python-nxt to python-pynxt, since it will get very confusing >>> if there is python-nxt and nxt-python >> There are two rules: >> >> - For python modules, the binary package name should be python-$mod, where $mod >> is what you import (so if you do `import nxt`, it should be python-nxt). > > This is the case for my package. I don't know if it's also the case > for pyrtc, but I guess so. > >> - Usually, first come, first serve. So it should be your package that should be >> renamed (unless there's a good reason not to). > > As I said I think it's easier to have python-nxt and python-pyrtc > then having python-nxt and nxt-python, since this would be really > confusing IMHO. But perhaps you've got better ideas? Since the other package was never uploaded, I wouldn't have any problem with you taking over that name, but let's hear other opinions. Where does python-pyrtc come from BTW? Cheers, Emilio
Attachment:
signature.asc
Description: OpenPGP digital signature