[zypp-devel] Updater applet for Gnome and KDE
The openSUSE updater is a desktop applet which shows the user the available updates (patches). It is very light and simple as the real work is done by the YaST solver. This allows us to provide one applet per desktop, much like you have a a NetworkManager applet per desktop. The KDE applet was born last year as a Google SoC project. Today I imported the opensuseupdater KDE applet sources from berlios to svn.opensuse.org/svn/zypp. The gnome applet was already in the zypp repository. There is a new wiki page for both the KDE and Gnome applet. * http://en.opensuse.org/Updater_Applet The sources for both applets are located here: * http://svn.opensuse.org/svn/zypp/trunk/updater-gnome/ * http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_2-Branch/updater-kde... Also, there is a work branch for the KDE applet where a major refactoring is going on to cleanup legacy code from SoC, use cmake as build system and load the backends as KDE plugins. It will become trunk once it works: http://svn.opensuse.org/svn/zypp/branches/work/updater-kde-refactoring/updat... Just email me for any question! cheers -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On 4/10/07, Duncan Mac-Vicar Prett
The openSUSE updater is a desktop applet which shows the user the available updates (patches). It is very light and simple as the real work is done by the YaST solver. This allows us to provide one applet per desktop, much like you have a a NetworkManager applet per desktop.
The KDE applet was born last year as a Google SoC project. Today I imported the opensuseupdater KDE applet sources from berlios to svn.opensuse.org/svn/zypp. The gnome applet was already in the zypp repository.
There is a new wiki page for both the KDE and Gnome applet. * http://en.opensuse.org/Updater_Applet
The sources for both applets are located here:
* http://svn.opensuse.org/svn/zypp/trunk/updater-gnome/ * http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_2-Branch/updater-kde...
Also, there is a work branch for the KDE applet where a major refactoring is going on to cleanup legacy code from SoC, use cmake as build system and load the backends as KDE plugins. It will become trunk once it works:
http://svn.opensuse.org/svn/zypp/branches/work/updater-kde-refactoring/updat...
Just email me for any question!
cheers
Nice stuff. Are there any plans to have an option in the updater to make it work like an upgrader (bug #216097), as well? There was a discussion about this at a status meeting a while back, and it was generally concluded (also by AJ, as I recall) that it would be nice to have (very frequently-requested feature; zen-updater worked like that, even if it was a bug, and people really liked it) as an option, but not -- of course -- enabled by default. Kind thoughts, -------------- Francis Giannaros Web: http://francis.giannaros.org IRC: apokryphos on irc.freenode.net -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Tuesday 10 April 2007 17:10:41 Francis Giannaros wrote:
Are there any plans to have an option in the updater to make it work like an upgrader (bug #216097), as well? There was a discussion about this at a status meeting a while back, and it was generally concluded (also by AJ, as I recall) that it would be nice to have (very frequently-requested feature; zen-updater worked like that, even if it was a bug, and people really liked it) as an option, but not -- of course -- enabled by default.
That can be taken in consideration. What I don't like is that the amount of data going to the applet will increase. I only see the usecase for people using packman, but people using factory it is nonsense. Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On 4/10/07, Duncan Mac-Vicar Prett
On Tuesday 10 April 2007 17:10:41 Francis Giannaros wrote:
Are there any plans to have an option in the updater to make it work like an upgrader (bug #216097), as well? There was a discussion about this at a status meeting a while back, and it was generally concluded (also by AJ, as I recall) that it would be nice to have (very frequently-requested feature; zen-updater worked like that, even if it was a bug, and people really liked it) as an option, but not -- of course -- enabled by default.
That can be taken in consideration. What I don't like is that the amount of data going to the applet will increase. I only see the usecase for people using packman, but people using factory it is nonsense.
And Guru, some OBS repos (KDE, XGL/Beryl etc) too. I think it's important since these repos often contain a lot of favourite applications (like Amarok, KDE upgrades, etc) which people are always excited about finding out the new features of with the latest versions. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Tuesday 10 April 2007 17:59:21 Francis Giannaros wrote:
And Guru, some OBS repos (KDE, XGL/Beryl etc) too. I think it's important since these repos often contain a lot of favourite applications (like Amarok, KDE upgrades, etc) which people are always excited about finding out the new features of with the latest versions.
We could introduce some kind of flags to let the user add metadata to the repo like "tell me if there are new packages" and "tell me if there are new patches", with update repos having the second one by default. That way we could avoid loading factory into it. Right now the only smartness checkpatches does to avoid restoring unneded sources is bool Source::hasResolvablesOfKind( const zypp::Resolvable::Kind &kind ) const; which allows checkpatches to see if a source has patches, which is implemented only looking the index of a YUM repo, or false for SUSEtags repos. Now we are doing the refactoring we could introduce flags and tags. The second to integrate with the build service tagging. Also rating. Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Duncan Mac-Vicar Prett wrote:
On Tuesday 10 April 2007 17:59:21 Francis Giannaros wrote:
And Guru, some OBS repos (KDE, XGL/Beryl etc) too. I think it's important since these repos often contain a lot of favourite applications (like Amarok, KDE upgrades, etc) which people are always excited about finding out the new features of with the latest versions.
We could introduce some kind of flags to let the user add metadata to the repo like "tell me if there are new packages" and "tell me if there are new patches", with update repos having the second one by default.
That way we could avoid loading factory into it.
Another thing that would be of help here is the ability to use which install sources to use in a transaction. You will be able to choose guru or packman for upgrade. And this is among our plans already. However, the flags/tags you mention could be nice to use in other scenarios. jano -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGHJJOgEhGpmN+6QERAlYKAJ4jMrzuuWgpLVd8Kwk+lWx4NTlVxACeKLP+ JzB25yx4PKM64uQZaOty9Rg= =YUZr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On 4/10/07, Duncan Mac-Vicar Prett
On Tuesday 10 April 2007 17:59:21 Francis Giannaros wrote:
And Guru, some OBS repos (KDE, XGL/Beryl etc) too. I think it's important since these repos often contain a lot of favourite applications (like Amarok, KDE upgrades, etc) which people are always excited about finding out the new features of with the latest versions.
We could introduce some kind of flags to let the user add metadata to the repo like "tell me if there are new packages" and "tell me if there are new patches", with update repos having the second one by default.
That way we could avoid loading factory into it.
Right now the only smartness checkpatches does to avoid restoring unneded sources is bool Source::hasResolvablesOfKind( const zypp::Resolvable::Kind &kind ) const;
which allows checkpatches to see if a source has patches, which is implemented only looking the index of a YUM repo, or false for SUSEtags repos.
Now we are doing the refactoring we could introduce flags and tags. The second to integrate with the build service tagging. Also rating.
Might be nice, but I'm wondering if it's overkill in this situation, and if it might require too much other code. Thing is, if you have a repo X which is set to notify on upgraded packages, can you override that setting? If so, you'd perhaps need to add an extra option somewhere in openseupdater to enable/disable that. Then, wouldn't the YaST installation source module require such an option, too? You'd get a lot more configurability this way, but I'm not sure that it's necessary. What's so bad about having repos like Factory tell you about upgraded packages, anyhow? Presumably people using factory will know not to update every single package every few hours, anyhow, right? -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (3)
-
Duncan Mac-Vicar Prett -
Francis Giannaros -
Jan Kupec