Hi, I’ve just uploaded a new build of xmonad to make sure the build-dependencies match the ones in the archive.
I’m wondering if this strictness (setting the build-dependencies on haskell modules exactly to the version currently installed) is really needed. The policy only mentions it is used to keep the architectures in sync, but I don’t really understand the problem this is fixing. I’m also wondering if we can’t keep the archives in sync using binNMUs. I would think it saves us some work this way. It’s also nicer to our users who try to re-build a certain package on their local machine, without having the very exact build-dependencies installed. I’m probably missing some point here, but I’d like to learn about it. Thanks, Joachim -- 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
