During the review[0] of pyhunspell[1] some confusion came up. The current python module guidelines contain the following:
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28... | There is an exception to this rule. If the upstream source has "py" | (or "Py") in its name, you can use that name for the package.
For the project "pyhunspell", the tarball is currently called "hunspell-0.1.tar.gz". Therefore this exception does not seem to apply.
But the general naming guidelines allow to take the project name into consideration:
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming | When naming a package, the name should match the upstream tarball or | project name from which this software came.
Can the python exception please also allow to consider ther project name?
Regards Till
[0] https://bugzilla.redhat.com/show_bug.cgi?id=514509 [1] http://code.google.com/p/pyhunspell/
Till Maas wrote:
Can the python exception please also allow to consider ther project name? [0] https://bugzilla.redhat.com/show_bug.cgi?id=514509 [1] http://code.google.com/p/pyhunspell/
Seems clear to me that this is a worthy case for the py-exception. It's the project name that's important, not the tarball name, imo.
That said, upstream having project name != tarball name seems more than a wee bit silly.
-- Rex
2009/8/2 Rex Dieter wrote:
Till Maas wrote:
Can the python exception please also allow to consider ther project name? [0] https://bugzilla.redhat.com/show_bug.cgi?id=514509 [1] http://code.google.com/p/pyhunspell/
Seems clear to me that this is a worthy case for the py-exception. It's the project name that's important, not the tarball name, imo.
That said, upstream having project name != tarball name seems more than a wee bit silly.
As Rex suggested py-exception seems most apt, but a case worth for consideration for addition to guidelines so as to prevent future confusion.
Le dimanche 02 août 2009 à 08:54 -0500, Rex Dieter a écrit :
Till Maas wrote:
Can the python exception please also allow to consider ther project name? [0] https://bugzilla.redhat.com/show_bug.cgi?id=514509 [1] http://code.google.com/p/pyhunspell/
Seems clear to me that this is a worthy case for the py-exception. It's the project name that's important, not the tarball name, imo.
That said, upstream having project name != tarball name seems more than a wee bit silly.
It is very common. Project name == tarball name is really only used as a conventions in the C FLOSS community and a few sister ones. That's why the only rpm macro which is pretty much mandatory to learn for a packager is %setup.
packaging@lists.fedoraproject.org
-
Nicolas Mailhot -
Rakesh Pandit -
Rex Dieter -
Till Maas