sven.panne:

On Monday 02 April 2007 13:23, Donald Bruce Stewart wrote:

...

[...] The other compilers should be using a base package with fps in it, as hugs and ghc do.

fps as a package only exists as a seperate darcs repo for those systems that don't have bytestrings in base. I.e. older GHC's, and nhc98 (not Hugs or GHC 6.6).

Does that help clear things up? Effectively there is *no* fps package really -- its suppposed to be part of base, as ghc and hugs have it.

Hmmm, why does nhc98 explicitly retrieve the fps package from your repo then? It retrieves the same base package as GHC and Hugs, which should contain fps already. Malcolm?

Ah yes, I remember now. 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. So nhc should no longer need a seperate fps once we merge in those nhc patches to base, with the other fps 0.8 changes. -- Don

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 * nhc now has hGetBuf/hPutBuf Mon Dec 4 23:09:12 EST 2006 Malcolm.Wallace@cs.york.ac.uk * Fixups for building with nhc98 - inadvertently missed this file earlier. Thu Nov 16 22:34:10 EST 2006 Malcolm.Wallace@cs.york.ac.uk * workaround nhc98 import resolution bug for another module Thu Nov 16 22:26:51 EST 2006 Malcolm.Wallace@cs.york.ac.uk * 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 Malcolm.Wallace@cs.york.ac.uk * portability: give alternate import modules for nhc98 -- Don

On Monday 02 April 2007 15:44, Malcolm Wallace wrote:

Done (although with some reluctance due to the general network slowness of darcs.haskell.org). In the new darcs-all, I am very keen to retain the ability to use package repos stored elsewhere (not at darcs.haskell.org).

Thanks, that was quick. We can add general URL handling later, but initially I don't want to open too many cans of worms at once. :-)

...

* Finally, I am utterly confused by the fps package: Using it currently must be a nightmare for packagers/users due to this versionitis... :-/

Yup. To reduce this confusion, I would very much like fps to remain separate from base, and that is one reason (but not the only one) why nhc98 does not build or export the version of Data.ByteString in base.

:-/ That's the exact opposite of Don's intention, if I interpret today's mails correctly. So I'd like to propose that for the time being, we keep the "internal" version, fix it so it works with all implementations and leave the rest of the fps Jihad to future generations, where everything is a separate package, world hunger is solved, and all taxes are abolished... :-} Cheers, S.

Malcolm.Wallace:

Sven Panne wrote:

...

* Malcolm: Could you move the polyparse repository from http://www.cs.york.ac.uk/fp/darcs/polyparse to darcs.haskell.org/packages, please? This would make things more consistent.

Done (although with some reluctance due to the general network slowness of darcs.haskell.org). In the new darcs-all, I am very keen to retain the ability to use package repos stored elsewhere (not at darcs.haskell.org).

...

* Finally, I am utterly confused by the fps package: Using it currently must be a nightmare for packagers/users due to this versionitis... :-/

Yup. To reduce this confusion, I would very much like fps to remain separate from base, and that is one reason (but not the only one) why nhc98 does not build or export the version of Data.ByteString in base.

I too am happy to split it out -- as long as nothing in base is using PackedString or bytestring. But until it is split, and while Hugs and GHC both have it in base, hmm, nhc is playing odd man out ;-) -- Don

On Tuesday 03 April 2007 12:54, Malcolm Wallace wrote:

Sven Panne wrote:

...

* Iavor's package is called "monadLib", but the darcs repo on darcs.haskell.org is called "monad". I propose to simply rename that directory to match "monadLib".

s/monad/monads/

Ooops...

FWIW, this name change broke my overnight builds. Easily fixed, but there are other places that are impacted by the name change too, e.g. http://darcs.haskell.org/darcsweb

Some minor breakage could not be avoided, I guess. I've just fixed darcsweb. Cheers, S.