Re: Package versioning confusion

sven.panne:
> On Monday 02 April 2007 13:51, Donald Bruce Stewart wrote:
> > [...]
> > nhc does use a base containing ByteString *but* it needed a couple of
> > tweaks to compile. Those nhc patches are in the darcs repo, but not in
> > the standard base yet.
> >
> > They will be on the next merge. [...]
> 
> Could you merge just the nhc tweaks now or at least give me a hint what the 
> problems were? Resolving this issue right now would eliminate the need to 
> handle general URLs in darcs-all and make the whole situation a bit less 
> confusing. No code is good code...

I'm actually submersed in ICFP paper writing for the rest of the week, so
I doubt I'll get a chance to do the merge before Saturday. 

For reference, the relevant patches in fps' darcs repo are, I think:

    Thu Mar  1 20:44:00 EST 2007  Don Stewart <[email protected]>
      * nhc now has hGetBuf/hPutBuf

    Mon Dec  4 23:09:12 EST 2006  [email protected]
      * Fixups for building with nhc98 - inadvertently missed this file earlier.

    Thu Nov 16 22:34:10 EST 2006  [email protected]
      * workaround nhc98 import resolution bug for another module

    Thu Nov 16 22:26:51 EST 2006  [email protected]
      * Workaround for import resolution bug in nhc98.
      Where there are multiple renamed imports:
          import X as P
          import Y as P
          import Z as P
      and they all export or re-export the same entity e, nhc98 does not seem
      to be able to recognise that P.e is a unique entity, despite X.e, Y.e, and
      Z.e all referring to the same thing.  This patch just introduces an extra
      module name
          import X as S
      so that S.e is resolvable.

    Thu Nov 16 22:24:52 EST 2006  [email protected]
      * portability: give alternate import modules for nhc98


-- Don