RE: Haskell library infrastructure coordinator

Isaac Jones writes:
Here are some suggestions on how you might proceed usefully and give us some time to come up with a plan for a build system
- collect the libraries that are already included with various compilers and see what the differences are both in what libraries are included and behaviors of the libraries
Are you aware that the three main compilers (GHC, nhc98 and Hugs) are all working from the same set of library sources these days? In the CVS repository on cvs.haskell.org, in the directory fptools/libraries, are the libraries that GHC, Hugs and nhc98 are all shipped with. These libraries are maintained by various people. They follow the guidelines in the library document: http://www.haskell.org/hierarchical-modules/libraries/libraries.html I doubt that we want to replace these libraries with another distribution. Let's not forget: the problem which originally prompted this discussion is that this set of libraries is about as large as we can reasonably distribute with the compilers. The idea was to develop a build/distribution system to make it easier for third-party library developers to distribute their work, without relying on the compiler developers to do it.
- find orphaned libraries (ala Numeric Quest) and try to find the authors to give them licenses.
- some documentation for standards lightly based on the libraries currently included w/ compilers.
The document I referred to above has guidelines for library design.
These will probably want to include some reference to various licenses.
The document I referred to above has a section on licenses. Cheers, Simon

"Simon Marlow"
Are you aware that the three main compilers (GHC, nhc98 and Hugs) are all working from the same set of library sources these days?
Ahh, thats great. For some reason I've been thinking that fptools/libraries was only used by ghc. So all of the implementations pick up changes made to the cvs repository in fptools/libraries, or is it more ad-hock than that?
Let's not forget: the problem which originally prompted this discussion is that this set of libraries is about as large as we can reasonably distribute with the compilers. The idea was to develop a build/distribution system to make it easier for third-party library developers to distribute their work, without relying on the compiler developers to do it.
Indeed. I was also imagining that at least some of the libraries currently distributed with the compilers probably should be delivered seperately once we get the system set up. I also heard that nhc is using a forked version of Greencard for instance (this may be neither here nor there) which is the root of my comment:
- collect the libraries that are already included with various compilers and see what the differences are both in what libraries are included and behaviors of the libraries
So in general what I'm getting at is that a starting point for a new collection of libraries for distribution could be the libraries that are already distributed with the compilers, but maybe this should be the last thing we worry about. I'll let Peter Simons hash that out w/ the list. peace, isaac

On Wednesday 04 June 2003 4:57 pm, Isaac Jones wrote:
I also heard that nhc is using a forked version of Greencard for instance (this may be neither here nor there) which is the root of my comment:
We believe that NHC works with the version of greencard in the repository at the moment. (We haven't actually tried this because, until recently, nhc didn't implement the ffi faithfully enough to be worth trying. I believe this has now changed.) But... The NHC folks forked GreenCard and made a bunch of extensions to their copy in pursuit of their work on reducing size and overhead and used these extensions heavily in their libraries. So, if you want to build their libraries, you need their greencard but if you want to build a library for hugs and ghc, you need the official version of greencard. It would be good to review the extensions NHC's version provides and see which should be added to the official version and which can be dropped with little cost. This is probably best done by some third party that wants to use an NHC library with GHC/Hugs. -- Alastair
participants (3)
-
Alastair Reid
-
Isaac Jones
-
Simon Marlow