Re: naming package as a library or tool

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

 



On Tue, Aug 18, 2015 at 01:22:59PM +0530, Parag Nemade wrote:
>    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?

Subpackages are definitely the answer here. There are still several
rational options. If the tool is primary, making the main package be
the upstream name ("foobar") makes sense, with subpackage for the
library ("python3-foobar", "foobar-libs"). If the library is primary,
though, you might want to go for "libfoobar" and "libfoobar-tools".


-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
--
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