On Wed, Nov 27, 2019 at 09:49:32PM -0500, Chris wrote:
> + Richard: Thank you very much for sharing those references, I had a look
> into each specfile and first of... whoa... they're very big.... But one
> thing I noticed is nbdkit is slightly inconsistent with some of the other
> package (or vs versa?):
> * sub-packages in nbdkit are formatted as: 'ndbkit-{name}-{type}' (where
> {type} would be plugin) while other packages (such as libvirt) does it's
> sub-packages as 'libvirtd-{type}-{plugin}'. Is there a preference or a
> standard I should use?
In nbdkit we swapped the fields around so that the Fedora package
names are the same as what the upstream project uses
(eg. nbdkit-ssh-plugin).
However this is something you are free to choose for your own project,
so you might use <project>-<type>-<plugin> if you think that is
better.
> [generating subpackages using a Lua script]
What Tom has done for lodash is nice, if you can achieve it. The
nbdkit subpackages are rather non-uniform so it would be difficult for
that project.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
