[Bug 648986] Review Request: python-cups - Python bindings for CUPS

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=648986

--- Comment #5 from Jiri Popelka <jpopelka at redhat.com> 2010-11-18 09:25:39 EST ---
(In reply to comment #3)
> OK, let's wait for Tim's reply (here and in bug #648987).
> 
> The main point here is the exception: '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.' [In this case the upstream tarballs are named "pycups"
> and "pysmbc".]
>From my point of view the main point here is that you *can* use that (upstream)
name. There's no 'should' or 'strong suggestion'.

The paragraph says:
"
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. 
"

We use 'import cups' and 'import smbc' in Python scripts which gives me a
python-cups and python-smbc package names.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.