On Wed, Jan 20, 2016 at 11:54 PM, Zbigniew Jędrzejewski-Szmek wrote:
> Yes, the guidelines apply to the source rpm name too. Those
> srpms should be called python-*, because they contain python libries.
OK. Thank you.
And what is the best current practice if the library contains some
utilities. Should the utilities land in the python{2,3}-name package?
Should it land in both?
To give you an example, the ripe.atlas.sagan ships a utility
parse_abuf. I'm currently removing it from the package as the upstream
is going to deprecate it with the next release. But theoretically,
should the utility be included in python2-ripe-atlas-sagan as
parse_abuf2 and in python3-ripe-atlas-sagan as parse_abuf? Or would it
be better for instance to create a package ripe-atlas-sagan which will
contain just the Python 3 version of the utility?
Jan
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
