patch for containers library

[Ian Lynagh]

On Sat, Apr 09, 2011 at 07:31:09AM +0100, Malcolm Wallace wrote:
> >> It hardly seems worthwhile to convert the patch to git format, simply to have it in ghc's private repo.
> > 
> > It's not GHC's private repo, it's the official, central repo.
> 
> And how many compilers does the containers package from the git repo currently build with? :-)

The same number the package from the darcs repo did  :-)

> A two-way git/darcs mirror sounds ideal.

Two-way mirrors are tricky. GHC's are only one-way.

> Tarballs seem unlikely to be a solution, since there is no obvious way to contribute back build-fixes.  Unless the maintainers would accept plain old diff patches and roll a new tarball?

Plain old diffs are fine for patches, IMO. I wouldn't want to be
rerolling tarballs too frequently, though.

> Or, and I know this is asking too much, if the maintainers would themselves test patches on more than one compiler...  :-)

Would you be willing to run GHC's validate script before pushing any
patches?  :-)

I'd be keener on reducing the difference between the compilers (where
feasible) than in continuing to work around them, though.


Thanks
Ian