#263: Multiple compilers of the same version confuse Cabal ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Comment (by duncan): Personally my inclination is not to include the location by default. I wonder if there is a way of detecting if we're mixing things. The problem is not that we're corrupting the current ghc's package db but that we're overwriting the package that is registered with another ghc's package db. There is currently no way to map back to which package db it's registered in. Indeed it's not impossible for it to be registered in multiple package dbs. Still it might be useful to keep some pointer pack to which package db we think the package is registered in. Then if we were overwriting the files and registering into a different db then we'd know we were breaking the other db. If we ever go for a hashing system (to allow multiple instances of the same package built against different versions of their dependencies) then this would no longer be a problem since the package hashes would be different, and if they were the same then their content would also be the same so it'd also be ok. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/263#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects