12:55 p.m.
The way I interpreted the Package Naming Guidelines[1], the package I'm
working on (pysvn) should be called python-svn. Is this not correct[2]?
1: http://fedoraproject.org/wiki/Packaging/NamingGuidelines
2: https://bugzilla.redhat.com/show_bug.cgi?id=428718#c11
--Tim
______________________________________________
< Beer -- it's not just for breakfast anymore. >
----------------------------------------------
\
\ \
\ /\
( )
.( o ).
1:06 p.m.
On Thu February 14 2008, Timothy Selivanow wrote:
The way I interpreted the Package Naming Guidelines[1], the package
I'm
working on (pysvn) should be called python-svn. Is this not correct[2]?
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#head-8756a3bce65...
| 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. So, for
| example, pygtk is acceptable.
pysvn is a valid name for your package.
Regards,
Till
1:09 p.m.
Timothy Selivanow wrote:
The way I interpreted the Package Naming Guidelines[1], the package
I'm
working on (pysvn) should be called python-svn. Is this not correct[2]?
1: http://fedoraproject.org/wiki/Packaging/NamingGuidelines
2: https://bugzilla.redhat.com/show_bug.cgi?id=428718#c11
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#head-8756a3bce65...
"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. So, for
example, pygtk is acceptable."
-- Rex
1:27 p.m.
On Thu, 2008-02-14 at 13:09 -0600, Rex Dieter wrote:
Timothy Selivanow wrote:
> The way I interpreted the Package Naming Guidelines[1], the package I'm
> working on (pysvn) should be called python-svn. Is this not correct[2]?
>
>
> 1: http://fedoraproject.org/wiki/Packaging/NamingGuidelines
> 2: https://bugzilla.redhat.com/show_bug.cgi?id=428718#c11
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#head-8756a3bce65...
"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. So, for
example, pygtk is acceptable."
-- Rex
Thanks! Somehow I missed that little blurb under the examples. pysvn
also falls under the "how it is called" rule, as it is used as "import
pysvn". So many documents...
--Tim
____________________________________________________________________
/ It isn't necessary to have relatives in Kansas City in order to be \
| unhappy. |
\ -- Groucho Marx /
--------------------------------------------------------------------
\
\ \
\ /\
( )
.( o ).
1:50 p.m.
Timothy Selivanow wrote:
The way I interpreted the Package Naming Guidelines[1], the package
I'm
working on (pysvn) should be called python-svn. Is this not correct[2]?
1: http://fedoraproject.org/wiki/Packaging/NamingGuidelines
2: https://bugzilla.redhat.com/show_bug.cgi?id=428718#c11
For that package you could use either python-pysvn[1]_ or pysvn[2]_.
.. _[1]: 'They should take into account the upstream name of the python
module. This makes a package name format of python-$NAME. When in doubt,
use the name of the module that you type to import it in a script.' You
use "import pysvn" so $NAME = pysvn there.
.. _[2]: '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. So,
for example, pygtk is acceptable.' So a plain pysvn is fine.
-Toshio
5916
days inactive
5916
days old
packaging@lists.fedoraproject.org
4 comments
4 participants
participants (4)
-
Rex Dieter -
Till Maas -
Timothy Selivanow -
Toshio Kuratomi