[Fedora-packaging] naming package as a library or tool

Haïkel hguemar at fedoraproject.org
Fri Aug 21 19:21:44 UTC 2015


2015-08-18 15:13 GMT+02:00 Dominik 'Rathann' Mierzejewski
<dominik at greysector.net>:
> On Tuesday, 18 August 2015 at 09:52, Parag Nemade wrote:
>> Hi,
>>    Sometimes I get confused how to handle naming of a package where
>> package itself provides a nodejs or python library and wrapper/tool to
>> use that library.
>>    We have guidelines where it says if source is library from npmjs or
>> pypi then we should prefix package with nodejs or python but how to
>> name when source contains both?
>>    What gets precedence? name them with prefixes or just by tool name
>> or library name?
>
> I'm assuming you're split between python-foo and nodejs-foo, so how
> about naming the main package foo (it doesn't have to have any files,
> mind you) and creating two subpackages: python-foo and nodejs-foo out
> of it?
>
> Regards,
> Dominik

One could also leverage provides when splitting subpackages is not worth it.

ie: foobar provides a command-line (primary) and python2/python3 modules
=> foobar provides python-foobar and python2-foobar
=> python3-foobar (python3 variant)


> --
> Fedora http://fedoraproject.org/wiki/User:Rathann
> RPMFusion http://rpmfusion.org
> "Faith manages."
>         -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
> --
> packaging mailing list
> packaging at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/packaging


More information about the packaging mailing list