[aur-general] Python AUR tarball naming
I am updating some python tarballs in the AUR which appear to have been abandoned with the python switchover and don't have python3 versions. I created some python2 versions, named python2-foo, as this is what I thought was the correct practice, but found out the main(core, extra) python packages are not being renamed until python3 versions are available. So what is the correct practice? Should the old python tarballs be deleted and replaced by python2-foo versions or should the python tarballs just be made to work with python2? References: https://bbs.archlinux.org/viewtopic.php?pid=875851 https://bugs.archlinux.org/task/22636?events[0]=2&fromdate=&todate=&event_number=20&project=1&submit= -- David Campbell
On Fri, Jan 28, 2011 at 10:29 PM, David Campbell <davekong@archlinux.us> wrote:
So what is the correct practice? Should the old python tarballs be deleted and replaced by python2-foo versions or should the python tarballs just be made to work with python2?
Renaming should be done whenever it makes sense to do so. My opinion is that there's no point in renaming a Python package which only exists for Python 2. On the other hand, if you're uploading a new package, you might as well name it python2-foo.
participants (2)
-
David Campbell
-
Evangelos Foutras