#380: Ability to blacklist packages that are on hackage ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: wishlist blacklist | Difficulty: normal Ghcversion: 6.8.3 | Platform: ---------------------------------+------------------------------------------ Comment (by duncan): Chucking some extra constraints in is easy. The hard part is tracking them so we can report where they came from and if they were used. Saying that a package was not used due to blacklisting is quite hard really. I guess one could inspect the constraints at the end for each package and check if any packages were excluded only due to the specific blacklist constraint. If it was then we could check if that package would have been the preferred version vs the version actually picked. This relies closely on the way in which the current solver works and what internal method it uses and the information it collects. That's not great because we would like to make the algorithm pluggable so that we can easily experiment with improved algorithms. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/380#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects