Hi list, I’d like to bring up an old discussion again. In http://urchin.earth.li/pipermail/debian-haskell/2008-March/000386.html Ian explains the reasons for the strict build dependencies for haskell libraries. But there is a problem with the current way, that has bit me recently. Here is what happened:
1. haskell-x11 was updated and auto-built
2. xmonad, xmonad-contrib were uploaded, build-depending on
haskell-x11
3. xmonad and xmonad-contrib were tried at the same time, xmonad
succeeding, but xmonad-contrib failing, because xmonad was not
done yet.
4. manual intervention needed to “give back” (retry) xmonad-contrib
which obviously is not optimal.
Theoretically, there are "Dep-Waits", i.e. flags that tell the buildds
that a particular package should not be tried until the other version is
present. These are set when a package is uploaded, and would fix our
problem.
Unfortunately, they do not work well with == build dependencies, and it
seems for a reason[1] (it might be able to fix this, but that would
involve larger changes that I first thought). OTOH, >= build
dependencies would work great, and from what Ian said, this would be
sufficient for us.
Therefore I’m proposing to use >= for haskell library build-dependencies
in the future, to make auto-building less problematic. Ian, do you agree
with this conclusion?
Thanks,
Joachim
[1] http://lists.debian.org/debian-release/2008/07/msg00169.html
--
Joachim "nomeata" Breitner
Debian Developer
[EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ debian-haskell mailing list [email protected] http://urchin.earth.li/mailman/listinfo/debian-haskell
