> The best solution to me is having separate packages for plugins (a single package for mostly used ones, and a gtg-plugins-others for niche ones) on top of gtg sources, so we avoid of publishing two separate source tarballs. In Debian/Ubuntu this is easily doable, I don't know about Fedora.
We can simply create subpackages from the same source tarball if necessary (which is what I was planning to do here).
In case someone is wondering, this is true for all RPM-based distributions.
> The best solution to me is having separate packages for plugins (a single package for mostly used ones, and a gtg-plugins-others for niche ones) on top of gtg sources, so we avoid of publishing two separate source tarballs. In Debian/Ubuntu this is easily doable, I don't know about Fedora.
We can simply create subpackages from the same source tarball if necessary (which is what I was planning to do here).
In case someone is wondering, this is true for all RPM-based distributions.