Ralf Corsepius wrote:
For those cases, 2 approaches exist:
1) let all packages which provide such a plugin own the directory, they
install a plugin/add-on to (This is the approach, which is being applied
for packaging perl-modules)
This approach, however is only functional when all packages providing
such "plugins/add-ons" obey such a convention.
2) split out the plugin/add-on package into a separate package and let
this spit-out package depend on the "base-package".
There is a third possible approach:
Split out the plugin dir into a separate package and let
plugin/add-on packages depend on it.
However, both approaches, are only fully functional when all packages
providing such "plugins/add-ons" obey such conventions.
This stays true for all possible approaches.
Florian
--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging
