Next | Query returned 8 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2011-07-08 10:22:42 by PHO / phonohawk | Files touched by this commit (5) | Package removed
Log message:
-hs-cabal
   2011-01-17 11:48:03 by Emil Sköldberg | Files touched by this commit (17)
Log message:
Update maintainer email address to valid address.
   2009-11-10 10:31:56 by PHO / phonohawk | Files touched by this commit (3) | Package updated
Log message:
Upstream update to Cabal-1.6.0.3
   2009-10-11 12:44:40 by Thomas Klausner | Files touched by this commit (286)
Log message:
Remove obsolete @dirrm lines.
   2009-05-20 02:58:40 by Thomas Klausner | Files touched by this commit (75) | Package updated
Log message:
Recursive ABI depends update and PKGREVISION bump for readline-6.0 shlib
major change.

Reported by Robert Elz in PR 41345.
   2009-05-13 13:06:57 by Emil Sköldberg | Files touched by this commit (1)
Log message:
Completed the fix of the buildlink file.
   2009-05-13 13:05:29 by Emil Sköldberg | Files touched by this commit (1) | Package updated
Log message:
Fixed the buildlink file that was not updated properly after move
from wip/cabal
   2009-05-13 12:55:04 by Emil Sköldberg | Files touched by this commit (5) | Imported package
Log message:
Import hs-cabal-1.6.0.2 as wip/hs-cabal.

The Haskell Cabal is is the Common Architecture for Building
Applications and Libraries. It is a framework which defines a common
interface for authors to more easily build their applications in a
portable way. The Haskell Cabal is meant to be a part of a larger
infrastructure for distributing, organizing, and cataloging Haskell
Libraries and Tools.

Specifically, the Cabal describes what a Haskell package is, how these
packages interact with the language, and what Haskell implementations
must to do to support packages. The Cabal also specifies some
infrastructure (code) that makes it easy for tool authors to build and
distribute conforming packages.

The Cabal is only one contribution to the larger goal. In particular,
the Cabal says nothing about more global issues such as how authors
decide where in the module name space their library should live; how
users can find a package they want; how orphan packages find new
owners; and so on.

Next | Query returned 8 messages, browsing 1 to 10 | previous