98c3490196
We were packaging ydiff twice! In this patch, I've merged the two expressions into one, trying to take the best of each. ydiff (top-level) didn't support being used as a Python library, which is required by one other package (patroni), so I chose gitAndTools.ydiff as the starting point, then moved in the longDescription from the top-level one, as well as the code used to run the tests. While I was there, I fixed the tests, which were intended to be run by the top-level ydiff but actually were not, because unlike mkDerivation buildPythonApplication will not run `make test' by default. Also, top-level ydiff previously propagated less and patchutils, meaning they'd have been installed globally instead of just referenced by ydiff. gitAndTools.ydiff just did nothing. Both also expected to find git, hg, and svn in the environment, which was impure. So now all these programs are referenced by store path from ydiff, for purity. |
||
---|---|---|
.. | ||
default.nix |