python-nxt

[Sebastian Reichel]

Hi,

I'm not in the list, but I hope you will get the mail :) I just
packaged NXT_Python from http://home.comcast.net/~dplau/nxt_python/

After this I saw, that one of you packaged pynxt from 
https://ssl.natulte.net/nxos/devel and called it python-nxt,
too.

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
 - Can you check my package and upload it to debian afterwards? (I'm
   not a Debian Developer so far - but WIP :))

You can find my work @ http://elektranox.org/debian/python-nxt/

-- Sebastian Reichel


signature.asc
Description: Digital signature

Re: python-nxt

[Sebastian Reichel]

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 :)

> > 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?
 
-- Sebastian


signature.asc
Description: Digital signature