Hi,
Am Mittwoch, den 29.05.2013, 00:02 +0100 schrieb Colin Watson:
> I'm slightly creeped out that test-packages.pl didn't spot this, so I
> decided to steer clear and seek advice. Does it not notice test-suite
> dependencies? If not, it seems that we need something that does before
> bumping these dependencies, lest we break anything that still needs
> test-framework-{hunit,quickcheck2} 0.2.*.
yes, this is a shortcoming of test-packages.pl (or rather of
"cabal-install --enable-tests", which seems not to consider
build-dependencies of the tests, or if it does, it allows different
versions of dependencies of different the test suites, which makes sense
because they are not linked together in the end).
Another approach to testing the package set would be to retrieve
00-index.tar from Hackage, simply remove all packages not mentioned in
packages.txt and try to install all-packages.cabal from that. This would
also spot missing packages in all-packages.cabal directly.
Or maybe passing all configured packages addtionally as a --constraint.
Actually, I’ll try that right now.
Greetings,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part