Re: is the package plan broken

[picca <picca@debian.org>]

Ok, after installing a lot's of -dev packages, I can check the package 
plan.

$ CABAL_DIR=.cabal ./test-packages.pl
Reading packages.txt...
Reading lts.config...
Reading available versions...
Reading available binary versions...
Calculating availability...
Checking for outdated entries...
Updated:  List is 0.6.1 in the archive but 0.6.2 exists here.
Added:    clash-lib is 1.6.3 here but does not exist in the archive.
Added:    copilot-language is 3.10 here but does not exist in the 
archive.
Added:    crackNum is 3.2 here but does not exist in the archive.
Added:    hdf5 is 1.8.9 here but does not exist in the archive.
Added:    js-chart is 2.9.4.1 here but does not exist in the archive.
Added:    libffi is 0.1 here but does not exist in the archive.
Updated:  raaz is 0.2.1 in the archive but 0.3.6 exists here.
Updated:  regex-applicative is 0.3.3.1 in the archive but 0.3.4 exists 
here.
Creating fake global package db
Testing packages in 1 different groups
Running cabal-install (group default)...
1085 packages successfully tested for co-installability.
216 packages have newer versions on hackage

to my opinion on Salsa-CI pkg-config is not installed and cabal do not 
check the pkg-config dependencies.

Is there a way to teach cabal not to check for these pkg-config files, 
or should we install all the pkg-config dependencies before testing the 
package-plan ?

Cheers

Fred