On Sun, Dec 11 2011, Roman Cheplyaka wrote: > * Jose A. Ortega Ruiz <j...@gnu.org> [2011-12-11 08:43:01+0100] >> On Sun, Dec 11 2011, Brandon Allbery wrote: >> >> [...] >> >> > xmobar currently requires parsec 3.x; the above is the symptom of >> > building it against 2.x. >> >> Aha, thanks for pointing this out, guys. >> >> Peter, would using parsec 3.x be an acceptable solution to you? > > To avoid problems like this, please specify version constraints in the > .cabal file. See [1] for the details.
Thanks for your suggestion. Yes, that's what i was thinking of doing; but i wanted to know before that if there might be reasons for people not being able or not wanting to use parsec 3 (in which case i might try to rewrite the parsing code using parsec 2-compatible calls, assuming there's a compatibility layer in parsec 3). Cheers, jao -- One reason that life is complex is that it has a real part and an imaginary part. -Andrew Koenig _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
