On Feb 25, 2006, at 4:07 PM, David R. Morrison wrote:
So its only because we don't have a deb for (old) gettext-tools? If I built the old gettext-tools first it would be OK?
Gah, I've been getting things wrong. Lemme see if I can get this straight. We have these packages in stable:
gettext (-bin -dev -tools) 0.10.40-19 And in unstable: gettext (-dev) 0.10.40-24 libgettext3-shlibs (-dev gettext-bin gettext-doc) 0.14.5-1 gettext-tools (libgettextpo2-dev libgettextpo2-shlibs) 0.14.5-3The problem occurs on the upgrade from gettext 0.10.x in stable to gettext 0.10.x in unstable, right? I was getting this mixed up before, so you can neglect my last mail.
What we need then is to ensure that the old gettext-bin/tools are no longer installed at the time when the new gettext is installed. Either the gettext-bin/tools packages could be completely uninstalled, or they could be upgraded to the new gettext-bin/tools-- both situations would work.
It's still possible that adding to the new gettext Conflicts: gettext- bin (<< 0.14.5-1), gettext-tools (<< 0.14.5-1) would satisfy, I'm not sure how the dep engine would treat that. Or, we could be hacky and add 'fink build gettext-bin gettext-tools' to the new gettext's CompileScript, like we used to do in some other weird case.
I'm unsure what to do about valknut/dclib0, I'm not sure that there's any good way to tell fink that it needs to uninstall an old valknut, then build the new dclib0, then build and install the new valknut.
Dave
PGP.sig
Description: This is a digitally signed message part
