Re: preparing a 2.14 release

Can we revert the patch that causes issue 2541?  For me, the slowdown
is a strong enough reason to either compile a 2.10 for linux (which I
recall is tricky because you have to also install an old ghc) or
migrate off darcs.  I haven't done either yet because I mostly work on
OS X and the 2.10 binary is still available.  In any case, I think the
feature added "look for conflicting files" which makes everything so
slow is not worth making whatsnew so slow over.

I'm surprised there hasn't been a bigger fuss about this, maybe there
are no medium sized darcs repos left?

On Mon, Dec 11, 2017 at 6:34 AM, Guillaume Hoffmann <[email protected]> wrote:
> Hi all,
>
> there has been a recent breakage of darcs 2.12 build on stackage, and
> fixing it would require bumping several dependencies upper bounds,
> including base.
>
> Rather than doing that, I find more economical to prepare a release of
> Darcs 2.14. For this we need to fix the following:
>
> * windows compilation (broken by Ben's encoding changes)
> * make dependency on graphviz optional (hence the command `darcs show
> dependencies`) (see http://bugs.darcs.net/patch1626 )
>
> There are still bundles to review and tons of bugs to fix, but they
> are not blockers for a 2.14.0 release.
>
> Opinions?
>
> Guillaume
> _______________________________________________
> darcs-users mailing list
> [email protected]
> https://lists.osuosl.org/mailman/listinfo/darcs-users