'temporary' package

[Niklas Hambüchen]

I can follow Roman's point and don't find it overreacting.

When you're building software on which your success depends (e.g. for
your job or when it fuels your research), its very obstructing when the
ecosystem around you breaks, and you want it fixed as soon as possible.

Of course having your own fork for everything solves that, but it'd be
great to avoid that effort and it breaks a key good thing in the Haskell
ecosystem: For many things there's only one package that does it right,
and it would be nice to keep that up.

On 09/05/14 15:19, Erik Hesselink wrote:
> Aren't you overreacting a bit? It's only been two days since your
> initial email...
> 
> Erik