Re: naming package as a library or tool

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-- 
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@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux