Thinking about what's missing in our library coverage
ndmitchell at gmail.com
Fri Aug 7 04:18:07 EDT 2009
>> Yes, if the maintainer thinks its ready.
> The maintainer says that the library itself is definitely ready in its
> current state. :-)
This user definitely agrees!
> The only problem is that it depends on cpphs, which is not in the
> platform. I personally think that cpphs warrants inclusion in the
> platform too, but it comes with that same LGPL (+linking exception)
> "burden" that is already discussed (haskell-src-exts itself uses BSD).
> I see two possibilities:
> * Allow LGPL (+linking exception) in the HP and include cpphs. Then
> haskell-src-exts can replace haskell-src immediately.
I support this.
> * I remove the rather small functionality in haskell-src-exts that
> depends on cpphs (namely deliterating literate source files). Then a
> slightly stumped haskell-src-exts could replace haskell-src after I
> release such a stumped version.
I seriously dislike the idea that packages must have useful features
removed to end in the HP. I also want you to include CPP support in
HSE, and removing cpphs makes this more unlikely.
More information about the Libraries