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

Parag Nemade panemade at gmail.com
Thu Aug 20 03:03:42 UTC 2015


Hi,

On Tue, Aug 18, 2015 at 6:43 PM, Dominik 'Rathann' Mierzejewski
<dominik at greysector.net> wrote:
> 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?
>

I think I was not clear in my initial email. I actually combined
nodejs and python thing.

Recently I approved a elasticdump[1] package review where I just
suggested nodejs's first naming rule[2] to follow which will make it
nodejs-elasticsearch but submitter wanted to follow nodejs naming
guidelines second rule that says use tool name as package name. I was
fine with that so I approved but then someone offline discussed with
me same for python packaging. So I need some guidance here.

Regards,
Parag.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1231564
[2] https://fedoraproject.org/wiki/Packaging:Node.js#Naming_Guidelines


More information about the packaging mailing list