[Fedora-packaging] Inconsistencies in Python package naming

Stephen Gallagher sgallagh at redhat.com
Thu Mar 28 13:31:19 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/28/2013 08:47 AM, Rex Dieter wrote:
> On 03/28/2013 07:40 AM, Stephen Gallagher wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On 03/28/2013 08:32 AM, Rex Dieter wrote:
>>> On 03/28/2013 07:25 AM, Stephen Gallagher wrote:
>>> 
>>>> I have a related question, actually. We're splitting a
>>>> package out of the main 'sssd' package so that the
>>>> pure-python config API lives in a noarch package instead of
>>>> the main (arch-full) package.
>>> 
>>> If that "pure python config API" is a python module, then a 
>>> python- prefix is the way to go.
>>> 
>>> Though... it may also help frame the answer if you could
>>> describe the purpose of making the subpkg in the first place?
>> 
>> 
>> See https://fedorahosted.org/sssd/ticket/1839
>> 
>> 
>> - From my comments in the patch review thread: Rel-eng was
>> complaining that we had python modules contained in an 
>> arch-specific package that were being put on disk in a noarch 
>> location. Rel-eng made the incorrect assumption that this meant
>> that the modules were actually arch-specific, which they are
>> not; SSSDConfig is pure-python and safely noarch.
>> 
>> The correct solution to this is for us to add a
>> python-sssdconfig noarch subpackage and Requires: it from the
>> 'sssd' package (for backwards compatibility).
> 
> I'm not sure I would agree with the original assertion or this
> "correct solution" conclusion.  At least, it's not supported by our
> packaging guidelines anywhere that I'm aware of.  (or is it?)
> 


Well, I'm not sure it's specified in the guidelines anywhere, but I
think it does make sense to have noarch components stored in a noarch
package. Let's presume for the moment that splitting it out is
acceptable and talk more about the naming. In this situation, does
python-sssdconfig make the most sense as a subpackage name?

In essence, should we be treating all python packages as if they are
subpackages of python implementing some other application's
functionality, or should we be acting like MySQL (with their
MySQL-Python) subpackage?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFURicACgkQeiVVYja6o6OxagCfQs29ac1pJ6Ad7pck55Fbyi3I
T5IAnizE1jFAInhCh9RTK2AmPYFRs24R
=i3gn
-----END PGP SIGNATURE-----


More information about the packaging mailing list