[Mageia-dev] Python packaging policy

[Claire REVILLET]

Le 13/12/2012 15:43, Guillaume Rousse a écrit :
> Le 13/12/2012 15:24, Claire REVILLET a écrit :
>> Hi,
>>
>> Le 13/12/2012 09:00, Shlomi Fish a écrit :
>>> Hi Joseph,
>>>
>>> On Thu, 13 Dec 2012 14:53:04 +0800
>>> Joseph Wang<joequant at gmail.com>  wrote:
>>>
>> [...]
>>>> * I'd like to add a rule (which is followed by current packages) that
>>>> the prefix "py" should
>>>> generally be removed from a package name.  For example pyopencl
>>>> should be
>>>> called python-opencl.  This is the current convention for packages in
>>>> mageia.
>>> I'm OK with it either way.
>> I disagree on that point: software and libraries names are choose by the
>> developers.
>> Who are we to change them ?
> A free software distribution, whose part of the added value is overall 
> consistency. Which is out of scope of individual software authors by 
> definition.
>
> And the current issue is just about the *package* name, not exactly 
> the software name. Remember when 'thunderbird' was distributed as 
> 'mozilla-thunderbird' ?
>
> And just to compare it with other similar practices:
> - we already normalize perl version numbers, for sorting purpose
> - we already force lowercase package naming
> - we already modify software setup, to achieve FHS compliance
> - we already modify package behaviour, to prevent automatic upgrade, 
> for instance
>
> The two latest ones seems far most invasive IMHO than just shipping 
> pycups in a package called 'python-cups' rather than 'python-pycups'.
>
I understand your point, but i fear collisions between package names: 
(this is not a true example, i can't find one just now)
Imagine it exists "toto" and "pytoto" in the Python Package Index. It 
can happen just because some people don't feel the need to add "py" in 
the module name as it's already written in python and it's in the Python 
package index... which seems sensible.
Imagine "pytoto" is imported first with "python-toto" name for the package.
How should i name the package for "toto" ?

We can rename the first one into "python-pytoto" and import the second 
with "python-toto", but we have to take care of the packages with BR or 
R on the first one. And it will brake the new policy rule.

my 2 cents.
Claire