RE: Text.ParserCombinators.Parsec requires -package text.

Following up to my own message:

On 08 September 2004 10:26, Simon Marlow wrote:

> It is possible to have incompatible packages - i.e. packages that
> export identical symbols and so can't both be present on the link
> line.  The recent package proposal allows packages to overlap, so in
> order to implement the "link everything" idea we would be forced to
> include the package name in each symbol in a GHC-generated object
> file (we might need to do this eventually anyway, but without "link
> everything" we don't have to do it yet).
> 
> Not to mention incompatible C libraries: suppose I have two packages
> implementing Haskll layers over gtk 1.2 and 2.0 - I can't try to link
> both of those, even if the Haskell layers don't overlap.

But of course, you could implement "link everything" for just the
packages which are normally enabled by default (i.e. the ones marked
"auto", which currently correspond to the hierarchical ones).  These are
non-overlapping and link-compatible by definition, so that would work
fine.

This seems like a pretty good compromise to me.  To summarise: we do
Simon's suggestion except that we don't try to link packages which
aren't normally enabled by default, with Alastairs modification so you
have to explicitly disable packages if you don't want to link them.

Ok?

Cheers,
        Simon