
On 15/07/2009 18:10, David Menendez wrote:
On Wed, Jul 15, 2009 at 11:33 AM, Simon Marlow
wrote: On 15/07/2009 15:54, Ian Lynagh wrote:
On Wed, Jul 15, 2009 at 03:39:55PM +0100, Simon Marlow wrote:
But there's a solution: we could remove the "standard" modules from base, and have them only provided by haskell-std (since base will just be a re-exporting layer on top of base-internals, this will be easy to do). Most packages will then have dependencies that look like
build-depends: base-4.*, haskell-std-2010 We'll probably end up with situations where one dependency of a package needs haskell-std-2010, and another needs haskell-std-2011. I don't know which impls support that at the moment. That's the case with base-3/base-4 at the moment. Is it a problem?
Could I use two packages of arrow code which depend on base 3.0.2 and base 3.0.3, respectively, in the same project?
No. (though I'm not sure the significance of "arrow code" here). Is there a package that depends on base-3.0.2, and doesn't work with base-3.0.3? Cheers, Simon