Kim Wallmark <[email protected]> added the comment: Thanks for your feedback!
I think Petr is right to be grumpy about putting time in darcs.cabal. It causes a chicken-and-egg problem: Time is used in Distribution/ShellHarness.hs. Distribution/ShellHarness.hs is imported by Setup.lhs. Setup.lhs is what handles "cabal [anything]". "cabal configure" is what tells the user that they need to go install time. I think it's actually an insoluble loop. I'm not confident about other options, either. time (and the deprecated library oldtime) are the only things that provide wall-clock time. System.CPUTime is in base, but measuring elapsed time in CPU time wouldn't give us accurate information for long-running tests that are, for example, disk IO-bound. Making Distribution.ShellHarness a separate binary is going to make the connection between Setup and ShellHarness ugly for no good effect. I'm going to withdraw this patch and think about the problem more. It may not be possible to use non-base libraries in anything referenced by Setup.lhs. ---------- nosy: +KimWallmark status: needs-review -> rejected __________________________________ Darcs bug tracker <[email protected]> <http://bugs.darcs.net/patch62> __________________________________ _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
