On Thu, Mar 18, 2010 at 01:04:02PM -0800, Jeff Spaleta wrote: > So thinking in the context of how to build distribution packaging for > optional gpodder functionality I was wondering if it would be possible > to grow hooks into packagekit inside gpodder's interface so when a > user wants to enable optional gpodder functionality that required an > external package to be installed they can tick a radio box or click an > enable button or something which will then call packagekit via the > dbus hooks to install the necessary "something" that is missing on the > system...without going into the packaging manager at all on your own.
Sure - we've already prepared the "framework" for this inside the dependency manager code, but have been lacking integration of a specific packaging environment. See src/gpodder/gtkui/desktop/dependencymanager.py and its related TODO items in the source code for where the package manager-specific code has to be inserted. You probably also need to enhance the DependencyModel class in src/gpodder/gtkui/services.py with some additional metadata from the DependencyManager (in src/gpodder/services.py) so that you can map the command-line tool names and the Python module names to system-specific package names that need to be installed. Patches gladly accepted :) HTH. Thomas _______________________________________________ gpodder-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-devel
