Comment 2 for bug 591747

Speaking with my Debian/Ubuntu package maintainer hat on, I didn't pay too much attention to plugins required dependencies, say because it's clearly stated by gtg itself, say because some plugins are of little interest, and it's not worth the pain adding to Recommends full stack of required Python packages.

I must admit that it's not the preferred way to do this, because users expect gtg to work out of the box immediately, leaving apt/dpkg the task of installing dependencies, and this never happened since now. I can't blame users for reporting bugs, and "fixing" them by adding packages to Recommends falls into the first behaviour, which I want to avoid.

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.