#128: cabal building broken libraries when module list is not complete ----------------------------------+----------------------------------------- Reporter: m@tel.netbeisser.de | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-2.0 Component: Cabal library | Version: 1.1.6 Severity: major | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.6 | Platform: ----------------------------------+----------------------------------------- Comment (by duncan): To be honest I'd much rather spend time working on a proper solution than on intermediate hacky solutions like reading the output of `ghc -v2`. If someone else wants to implement that then fine I'm not totally against it but I don't really see it as a good use of our limited development time. The module/file dependency chasing is scheduled to be done by the end of the summer however that project only aims to make a prototype and demonstrate it on the case of pre-processors. I expect that it will take a bit longer before we are able to use it to replace the use of `ghc --make`. As for ticket #159, it's one of two existing prototypes for the make-style dependency problem. The GSoC project is pursuing a slightly different approach. I don't think package dependency resolution is the same problem as file/module dependency chasing despite initial similarities. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/128#comment:8 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects