Specifying dependencies on Haskell code

Ian Lynagh igloo at earth.li
Sat May 3 09:51:33 EDT 2008

On Fri, May 02, 2008 at 09:55:32AM -0700, David Roundy wrote:
> On Sun, Apr 20, 2008 at 09:22:56PM +0100, Duncan Coutts wrote:
> > 
> > We settled on a fairly traditional model, where one specifies the names
> > and versions of packages of Haskell code.
> Do you actually have any precedent for such a system?
> I know there is a long history of the autoconf-style approach being
> successful.  Can you point to any success stories of the approach chosen
> for cabal?

LaTeX does things like

According to http://peak.telecommunity.com/DevCenter/PythonEggs, with
python eggs you do things like
    from pkg_resources import require

According to http://blogs.cocoondev.org/crafterm/archives/004653.html,
with Ruby gems you do things like
    s.add_dependency("dependency", ">= 0.x.x")

(URLs found by googling for "how to make a <foo>")

Those were just the first 3 things I thought of.
I don't know what you would consider a success, though.


More information about the Libraries mailing list