Dominique Leuenberger napsal(a):

...

I think easier way is only remember package which user want explicit install (like you click on something in YaST and few others is also checked, so remember only first...same in zypper). Then make call like remove obsolete, which take this list of packages and create tree of its dependencies (also apply soft and hard locks). And uninstall everything which is not in this tree of dependencies. Pepa

Be careful with packages that were installed using rpm directly. You will not have them in your list of being 'requested' by the user. Always removing them would certainly not be a good idea though.

Dominique

same problem have previous sollution, because we remember only dependencies of package installed by libzypp frontend (yast, zypper...). So when you install some dependency via rpm, then we don't know it. Pepa -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Dominique Leuenberger wrote:

...

same problem have previous sollution, because we remember only dependencies of package installed by libzypp frontend (yast, zypper...). So when you install some dependency via rpm, then we don't know it.

Pepa

Indeed, but I think it's less 'risky', as we will probably not rip out any dependency that we see is still in use. If we remember only leaf packages, and remove all leaf packages that are not in use, we get out all the addons a user might install.

You can detect and remember packages installed by RPM as explicitly installed. There should exist a GUI to view explicitly tagged packages, to tag and untag them as explicitly required. Additionally it would be very useful to save this list and even make this list as an optional start point for package installation on upgrade or fresh install to another partition (it would require evaluation of provides/obsoletes on top of this list).

If we remember all the dependencies that were pulled it automatically and only care for those, all leaf packages and dependency packages a user installs (using rpm or on request using zypper) are not in the automatic dependency tree and are thus not affected.

It is still possible to offer "Full dependency cleanup". It exist for example in Gentoo as depclean. It is very dangerous there. Depclean would be a very powerful dependency exercise for our packages. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Michael Andres wrote: [...]

I'm currently looking into the Boost signals and slots library to see how we can use it to manage those connections. Signals represent callbacks with multiple targets. This is something our callback implementation lacks.

BTW do you know libsigc++? (http://libsigc.sourceforge.net/) I used it in a small project in the past. I don't know Boost signals, but it could be another candidate to consider if Boost would not fit our needs... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org