On Mon, Jul 18, 2011 at 10:34, Uwe Gansert firstname.lastname@example.org wrote:
on Friday 15 July 2011 Hans-Joachim Ehlers wrote:
Does these looks have any purpose except to drive me crazy ?
no, that was the only purpose ;)
No, seriously, back then, when I wrote that code for <remove-packages>, the taboo for packages was the only reliable way to tell the resolver "believe me, I don't want that package". The resolver always wanted to reselect the package unless it was on taboo. In the meantime the zypp resolver is a lot smarter and I should check that code again to replace it with something better because I think taboo is no longer needed unless you want to "remove-package" a package that is required by another one - then only taboo helps. I'll put that on my todo
In some cases, I find the locks quite helpful. Maybe just rename "remove-package" to "taboo-package" (or "(b)lock-package" or something like that) and write a new and shiny "remove-package"? I'd guess the number of people using (the current) remove-package for its locks is quite small, so the backward compatibilty issue would be quite small. Please, anybody using it that way, raise your voice now. (;
On Mon, Jul 18, 2011 at 10:54, Hans-Joachim Ehlers HansJoachim.Ehlers@eumetsat.int wrote:
you can remove the /etc/zypp/locks file in an init-script or so. Then all locks should be gone.
I have already extended our current init script to remove the looks via an /usr/bin/zypper --non-interactive rl *
The latter is the documented way to go, but if you use it on embedded hardware, it really makes a difference in terms of speed. While "rm /etc/zypp/locks" only takes a second to remove all (~500) locks, "zypper rl" takes about 25 minutes.