[aur-general] Should I have python-mongokit deleted?
I'm currently maintaining python-mongokit and python2-mongokit. python-mongokit is currently for Python 2 pending release of a Python 3 version. Should I have python-mongokit removed for now? I can't find a clear policy regarding that.
-Aaron DeVore
Den 25-01-2013 21:27, Aaron DeVore skrev:
I'm currently maintaining python-mongokit and python2-mongokit. python-mongokit is currently for Python 2 pending release of a Python 3 version. Should I have python-mongokit removed for now? [...]
For naming consistency, I'd probably suggest you request having python-mongokit merged into the python2 one, and then upload a new python-mongokit once a Python 3 version is released upstream.
That way, people won't think they're installing MongoKit for Python 3 with the python- package.
Hi,
Yes, there doesn't seem to be a clear policy on this. On one hand, removing python-mongokit and just keeping python2-mongokit until mongokit for python3 is actually available, is the cleanest solution for AUR as a whole. On the other hand, python-mongokit was python 2 previously, so requiring it to immediately transition to the "python2-" name is a hard requriement to fullfill. There are still several "python-" packages in AUR that are for python2. As far as I know, we have no set time limit for when all python2 packages should be named "python2-" in AUR and all python 3 packages should be named just "python-". There even seems to be some controversy if this is a good naming scheme at all.
tl;dr Both solutions should be fine, for now.
The answer from Frederik S. Olesen is a good one.
participants (3)
-
Aaron DeVore
-
Alexander Rødseth
-
Frederik "Freso" S. Olesen