Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=781687 --- Comment #8 from Hans de Goede <hdego...@redhat.com> 2012-01-19 05:28:25 EST --- (In reply to comment #7) > OK. > > AS for lv2core I've been having a bit of a rethink. For the sake of argument, > the spec could be extended at anytime leading to the creation of more > directories under %{_includedir}/lv2/lv2plug.in/ns . Changing lv2core each > time > the framework is extended by a new LV2 bundle seems a little unwieldy. Should > we leave each plugin owning the directories it drops files into rather than > giving ownership of ext/extensions to lv2core? My preference would be to have lv2core-devel own: %{_includedir}/lv2/lv2plug.in/ns/extensions While the plugin itself would own (in lv2-ui's case): %{_includedir}/lv2/lv2plug.in/ns/extensions/ui As for your worry that we then need to change lv2core each time we package a plugin from a new bundle. I think that you should have a reasonable idea about which bundles exist right now, so we could just make lv2core-devel create and own the necessary deps for all bundles from which we expect to package more then 1 plugin. I agree that if some rather exotic bundles pop up, that we should just let the plugins in that bundle also have shared ownership of the %{_includedir}/lv2/lv2plug.in/ns/<bundle> dir. But for something like extensions it seems sensible to me to make lv2core-devel own it rather then make a gazillion lv2-foo-devel packages have shared ownership of it. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review
