On Feb 25, 2006, at 11:23 AM, David R. Morrison wrote:
2. Even if we don't tell dpkg to install both at once, the SysState algorithm will figure things out in the simple cases, when upgrading the depender fixes things. For example, say you have foo-shlibs-1.0-1 and foo-dev-1.0-1 installed with the usual Depends: foo-shlibs (= 1.0-1). If you try to install foo- shlibs-2.0-1, SysState will figure out that foo-dev needs to be upgraded as well.Right. In both of your examples, the packages are splitoffs of the same parent, and its clear how to make SysState handle such a situation.
My example for SysState's algorithm involved splitoffs, but that's not necessary. It works just as well with non-splitoffs.
The problem with gettext is that when you build and install libgettext3-shlibs, the new gettext-tools hasn't been built yet! Even though SysState *wants* to upgrade them as a unit, it can't do so until it has .debs for all of them. The most sensible solution may be to build gettext-tools at the same time as libgettext3-shlibs, I'm not sure what the reasoning is for building them separately.
Otherwise, maybe we should make libgettext3-shlibs Conflicts: gettext- tools (<< whatever), so that old gettext-tools are removed before we try to upgrade libgettext3-shlibs. I'm not sure how well the dep engine will deal with that solution especially in the dclib0/valknut case, but it may be worth a try.
Dave
PGP.sig
Description: This is a digitally signed message part
