On Sun, 2010-03-21 at 13:15 -0400, Leon Smith wrote:
As somebody who's hacked on cabal-install a bit (but don't have a
worthwhile patch to contribute (yet?)), I can tell you that versions
support a tag structure, at least internally, but I haven't seen a
non-empty tags field and don't know
The documentation for Data.Version might be insightful:
http://haskell.org/ghc/docs/latest/html/libraries/base-4.2.0.0/Data-Version.html
If Cabal uses the parseVersion function to parse versions then the
following version is valid: 1.2.3-a-b-c. If should result in this
value:
Version
On Tue, Mar 23, 2010 at 10:00 AM, Roel van Dijk vandijk.r...@gmail.com wrote:
The documentation for Data.Version might be insightful:
http://haskell.org/ghc/docs/latest/html/libraries/base-4.2.0.0/Data-Version.html
If Cabal uses the parseVersion function to parse versions then the
following
If you're making local changes against a library you don't own (with
the ultimate intention of sending those changes back upstream to the
library maintainer) it makes sense change the version number to avoid
clashes with the canonical version of the library.
Of course, it's easy to lose track and
Hi Dougal
Could you prefix or suffix the forked package name in the cabal file
instead, then choose the appropriate one when you use GHC with the
-package-name flag?
Best wishes
Stephen
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
As somebody who's hacked on cabal-install a bit (but don't have a
worthwhile patch to contribute (yet?)), I can tell you that versions
support a tag structure, at least internally, but I haven't seen a
non-empty tags field and don't know how to make the tags field
non-empty. For that I'd
On Sun, Mar 21, 2010 at 5:15 PM, Leon Smith leon.p.sm...@gmail.com wrote:
As somebody who's hacked on cabal-install a bit (but don't have a
worthwhile patch to contribute (yet?)), I can tell you that versions
support a tag structure, at least internally, but I haven't seen a
non-empty tags
