Re: test-packages.pl
> > Would not it be more efficent to download only cabal files for packages
> > we are concerned with? Here is the plan:
> > [...]
> > Did I miss something?
>
> yes: When we plan to package new packages, it is important to have all
> of hackage available. My steps are:
>
> * Add new package foo to the plan.
> * run test-packages.pl
> If it finds a plan it will print all the extra dependencies that
> were pulled int.
> * I add the dependencies to the plan.
Okay, I understand, you have another workflow. Could you please
reconfigure Jenkins to build not only master, but also another branches?
This way I could try another (described above) implementation on
separate branch and check, that it does not produce false-positives?
Reply to: