Reinier Lamers <[email protected]> writes:

>  * We depend on a new version of haskeline, that depends on a new version of
>    utf8-string
>  * We specify a utf8-string dependency in darcs.cabal, only to make sure
>    the version haskeline uses is recent enough.
>
> The second option feels dirty, and I'm not sure if it works (if I compile
> haskeline against a buggy utf8-string, and then install 0.3.6 to keep the
> darcs installation happy, won't darcs still call the buggy utf8-string via
> haskeline?). That's why I suggested a new haskeline release.

As I understand it, the point of this is to prevent users accidentally
building against an old utf8-string which has a known bug.

Something similar was done for the 2.3.1 release with hashed-storage.
Since the newer hashed-storage isn't packaged for Debian yet, I can't
package Darcs 2.3.1 for Debian -- effectively meaning that the
well-meaning dependency tightening blocked ALL other bugfixes in 2.3.1.

(Hm... on reflection, I suppose I could've made a Debian-specific patch
to lower hashed-storage's lower bound in darcs.cabal.)

Anyways, the idea in my head at the start of this post was: "gee,
wouldn't it be nice if there were build-recommends?"  It occurred to me
that this might be approximated by having with a curl-pipelining-style
flag:

    flag no-known-bugs-in-deps
      description: when set to false, allow compilation against
        library versions with known bugs.
      default: True

    if flag(no-known-bugs-in-deps)
      depends: foo >= 1.1
    else
      depends: foo >= 1.0

But I'm not sure how to make cabal emit the warning...  I thought I
saw HTTP or curl emit one sometime.  Maybe they do it by

    if ! flag(no-known-bugs-in-deps)
      cflags: -DNAUGHTY_USER

And then in a .hs file, something like

    #ifdef NAUGHTY_USER
    #  warn You're linking against a buggy library!
    #endif

Given my parenthetical observation above is an adequate solution, I
suspect my rambling can simply be ignored.  Posting anyway just in case
there's a good idea in there somewhere.

_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users

Reply via email to