[Haskell-cafe] developing against privately patched libraries, and cabal

Leon Smith leon.p.smith at gmail.com
Sun Mar 21 13:15:09 EDT 2010

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 have to go source-code diving again.



On Sun, Mar 21, 2010 at 10:58 AM, Dougal Stanton
<dougal at dougalstanton.net> wrote:
> 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 end up publishing your own
> program against a non-existent (outside your hard disk) version of the
> library. I'd like to make it very obvious, both in mypogram.cabal and
> library.cabal that one is a patched copy and the other has to be
> compiled against a patched copy.
> Does cabal provide any way of marking a version private? I thought
> initially to just mark the version field in the patched library as
> X.y-dougal and enforce my program to compile against that, but it
> doesn't seem to recognise the -dougal suffix there.
> Thoughts?
> D
> --
> Dougal Stanton
> dougal at dougalstanton.net // http://www.dougalstanton.net
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe

More information about the Haskell-Cafe mailing list