Parsec => libraries

[Sven Panne]

Because of some ugly dependencies in my OpenGL stuff (some parts need the
text package, which hasn't been built by the time it's needed), I'd like
to see Daan's Parsec moved to Text.ParserCombinators. But I'm a bit
unsure about the structure: IIRC we agreed that there are many useful
parser combinator packages around, so they should go into their own
sub-package. So there should probably be a Text.ParserCombinators.Parsec,
right?

Another question: Where should examples and/or documentation for a
specific package go? It would be nice if we could settle for generic
naming scheme, e.g. the obvious

    Foo/Bar/Baz/doc        subdir containing documentation for package Foo.Bar.Baz
    Foo/Bar/Baz/examples   subdir containing examples for package Foo.Bar.Baz

If nobody else volunteers, I could do the move to the new library
hierarchy, i.e. from ParsecFoo to Text.ParserCombinators.Parsec.Foo.

Cheers,
    S.