On Thu, 19 Nov 2009, Daniel Fischer wrote:
A separate package for that orphan instance would be the best solution.
I'm not sure that's really better. With a separate package, you'd have
dependencies
packageY, orphanInstance.
When a new version of packageY with the instance is uploaded, things break in
the same
way. The fix is easy either way, delete the dependency orphanInstance or delete
the orphan
instance, but with a separate package, that stays around polluting hackage - or
is there
now a way to remove packages from hackage swiftly?
This interim package can be modified in a way such that it exports an
empty module for the versions of the base package that define the instance
themselve.
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
