gtg team mailing list archive

[Luca Invernizzi <invernizzi.l@xxxxxxxxx>]

That's a complex question :). Here's my ideas:

1. splitting the plugins into a subpackage

2. making the gtg-plugins package require the necessary Python modules
3. making sure those modules are properly packaged in Fedora
If someone wants to have a single plugin, it has to install the whole package dependencies. The tomboy plugin, for example, does not require any additional module, but to have it you will need to install python-geoclue. I'm almost sure that in the necessary modules for the geolocalization plugin are not packaged in fedora (they aren't in ubuntu), and they're quite unstable.
IMHO, this is not a great solution, as it gives you additional work without great benefit for the users (well, they'll have the geolocalization plugin working :) ).

4. eventually, if that's worth it, splitting each plugin in its own subpackage, each one requiring its own Python dependencies.
This is better, but gives all the packages a lot of work. From the user standpoint, plugins will not be "advertised" as they are now, so they might miss them.

For the debian&co distributions, a good solution is providing apt://
links. The user just need to click on that to install the required
modules. Does fedora have something simiar? Otherwise, we could pop out
a terminal with the yum (I believe) line to install the package. It's
far less beautiful than apt:// links, but it would work.

GTG devs, what do you think?


ps: Thanks for packaging GTG!

-- 
Split plugins in separate packages (in Fedora)
https://bugs.launchpad.net/bugs/591747
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: New

Bug description:
>From bug 493269, by https://edge.launchpad.net/~bochecha
=====================================================

(Disclaimer: I co-maintain GTG in Fedora)

Just for the record, I think this is a packaging issue in Fedora.

I had seen the issue and was planning on fixing it properly in the package by:
1. splitting the plugins into a subpackage
2. making the gtg-plugins package require the necessary Python modules
3. making sure those modules are properly packaged in Fedora
4. eventually, if that's worth it, splitting each plugin in its own subpackage, each one requiring its own Python dependencies

Like I said, I wanted to do that when I would find the time, and obviously discuss that with upstream GTG (i.e. you). I don't have the time right now, but I just found this bug report, so I guess this is a rather good place to open this discussion.

So what do you think? Does splitting the plugins from the core GTG make sense from a packaging perspective? Does splitting each plugin in its own subpackage make sense?

What's your take on this?

PS: I didn't want to reopen the bug as it's a slightly parallel issue and it's relative to a downstream distributor, should this bug be reopen? Should I open a new one?