[aur-general] need advice on package naming
Hi, I packaged python-libgit2 but the upstream is dead. And a new Python binding was started by the same team than libgit2 itself. It's named pygit2. So I wonder whether I keep the same package but point to the new repository (and thus follow the Python naming convention) or I keep the upstream name for people to find it (and follow packages like pygobject). Is it more important to prefix Python packages with "python-" or to respect the upstream name. In the former, I'll write down "pygit2" in the package description. In the latter, I'll ask for my old package to be deleted. Thanks for your advice. -- Hervé Cauwelier
2010/11/18 Hervé Cauwelier <herve@oursours.net>:
Hi,
I packaged python-libgit2 but the upstream is dead. And a new Python binding was started by the same team than libgit2 itself. It's named pygit2.
So I wonder whether I keep the same package but point to the new repository (and thus follow the Python naming convention) or I keep the upstream name for people to find it (and follow packages like pygobject).
Is it more important to prefix Python packages with "python-" or to respect the upstream name.
In the former, I'll write down "pygit2" in the package description. In the latter, I'll ask for my old package to be deleted.
Thanks for your advice.
Your choice, but it's common practice to follow upstream. You can upload a new pygit2 package, which would have a provision for python-libgit2. But I can't say anything about the python naming scheme - our repos still have both regular and pythonish schemes for python modules. Python apps, on the other hand, can have regular names.
participants (2)
-
Hervé Cauwelier
-
Ray Rashif