On Mon, Feb 13, 2017 at 08:46:19PM -0500, Randy Barlow wrote: > Is it ok to just name my source package js-qrcode-generator and package > just the js bits of it, or do I need to name my package qrcode- > generator? If the latter, would I be compelled to package all those > language implementations as subpackages, or could I package just the JS > one for now and wait to see if anyone files an issue to request the > other languages in the future? I'm not very familiar with the packaging > guidelines for all of those languages, so it would be tricky to get it > right for all of them. I'm something of an expert in packaging one source package -> multiple language bindings because of this and a few other packages: http://pkgs.fedoraproject.org/cgit/rpms/libguestfs.git/tree/ It's a pain! I would say in your case: (1) Give the source code package a generic name (qrcode-generator). (2) Package up the javascript bindings. (3) Let others create subpackages for the other bindings in future on an as-needed basis (and make them become co-maintainers and do the work :-) You ought to give the Javascript output subpackage a different name from the source package, to facilitate the other subpackages being created in future. Otherwise you'd end up needing to rename the JS subpackage in future which can be a pain. It's possible with recent rpmbuild to have the output name be completely different from the source name. For an example of this, see: http://pkgs.fedoraproject.org/cgit/rpms/xorg-x11-server.git/tree/xorg-x11-server.spec (note there is no %files section at all) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
