Hi, Splitting out a library from cabal-install have been a goal for a long time. I don't know if we want to just expose every module that's there today or if we'd like to think a bit more about the API first. Duncan, what do you think?
-- Johan On Sun, Dec 30, 2012 at 7:09 PM, Mikhail Glushenkov <the.dead.shall.r...@gmail.com> wrote: > Hi all, > > I'm currently looking into #1159, and I'd really like to add some unit > tests for the UserConstraints parser. The problem is that I can't > access modules defined under Distribution.Client.* without doing > unnecessary recompilation. Would it be fine if I split cabal-install > into library and executable parts in the following fashion: > > Library cabal-install > Build-depends: ... > ... > > Executable cabal-install > Main-is: Main.hs > Build-depends: cabal-install == N.N, ... > ... > > Test-suite unit-tests > Build-depends: cabal-install == N.N, ... > ... > > -- > () ascii ribbon campaign - against html e-mail > /\ www.asciiribbon.org - against proprietary attachments > > _______________________________________________ > cabal-devel mailing list > cabal-devel@haskell.org > http://www.haskell.org/mailman/listinfo/cabal-devel _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel