Paul van Tilburg a écrit : > Hi, > > On Mon, Feb 16, 2009 at 08:06:32PM +0100, Guillaume Emont wrote: >> The Elisa team is happy to announce the release of Elisa Media Center >> 0.5.28, code-named "Wooden Nickels". > > Very nice release. I am happy with it, thanks!
Hi Paul, Thanks, and sorry for the late reply. Have you checked out the latest release (0.5.32)? >> This release is a "light weight" release, which means it is supposed to >> be pushed to the users through our automatic plugin update system. [...] >> Tarballs are provided for packagers who want to disable the automatic plugin >> update system on their distribution, so that they can make new packages for >> their users to be able to update (I strongly advise that, the new video >> section >> is worth it). > > I am one of the Debian Elisa maintainers and am not sure how to deal > with the update system yet. I've talked about it with some of you > on the IRC, but it might be better to discuss it here. Indeed there is a lot to be discussed. > It seems there are a few issues here: > > 1) There are plugins that are not distributed via -good, bad, or -ugly > AFAIK (apple_trailers, ted, etc.). For this the plugin (update) > system is essentially an installer for extra functionality that users > can select. If these plugins are never pulled into -good, -bad or > -ugly, they should be updated once the user installs them. Either > that, or we start distributing these plugins also. The plugin distributed externally are indeed never going to be shipped in -good, -bad, -ugly. In fact for some of them (and we hope most of them in the future) we don't even ship them, just link to them in our plugin repository. That allows us to easily bring to the users the best of the community developments. Now, I would say that's up to each distro to decide whether they find some external plugins good and interesting enough (and license-compatible) to ship them in external packages. > 2) It might be that a user installs Elisa on a stable system, doesn't > want to jump to unstable to keep track of Elisa updates and chooses > to enable the plugin system (which IMO should be an option still). > Once the user jumps to a new stable release, the plugins in his > ~/.elisa-xxx/ are obsoleted and can be removed. Does Elisa to plugin > cleaning? Currently not, that's something we need to implement. See https://bugs.launchpad.net/elisa/+bug/309161. > 3) Is Elisa aware of plugins (including the core) being not user but > distribution installed? Yes. Basically, at startup plugins are going to be searched in the PYTHONPATH + ~/.elisa-0.5/plugins/. If a more recent version of a distribution installed plugin is found in ~/.elisa-0.5/plugins/, it is going to supersede it. > If (3) is the case, we could maybe have an mode between completely > unawareness of any plugin updates at all and full plugin upgrades and > access to new plugins that Elisa has now, namely a 'dist' mode where > dist plugins are never upgraded, only new plugins can be installed and > updated. Also plugins that become 'dist' plugins at some point can be > cleaned automatically. That's a possibility indeed, that would require some modifications to the plugin registry. In fact I want to clean it up at some point, and this feature could be implemented at this point. Can you please open a bug report explaining the idea, and assign it to me? > I have no idea if this is even possible and whether this would involve a > lot of work, I'm just expressing some ideas here. > > Your thoughts? A lot of very relevant remarks, and still a lot of work for us to get a really cool plugin system :) > > Kind regards, > Paul Cheers, Olivier
