On Tue, 22 Apr 2008 16:14:34 +0200 Juliusz Chroboczek <[EMAIL PROTECTED]> wrote:
> The clean and flexible way is to have an easily scriptable Darcs. > Darcs is fairly scriptable right now -- things like vc-darcs use Darcs > as is, with no need to link against a libdarcs. Two of my projects rely on the ability to "fetch" information and "interact" with darcs. One of them in particular, tailor, has the ambition of "talking" to several kinds of VCs at the same time, so I may be a little biased here, but I heartly agree with Juliusz. To quote Zooko, "CLI is the most stable API" :) It is a fact that the backend the needs my attention more often due to (crazy/little) changes to the API is the mercurial one, which is even written in Python. The darcs backend is the older one, and I'd say it was the most easy to get working, and the one that I change less often in absolute. I would not get any real advantage, from my "user-of-the-API POV", from dealing with, say, a C wrapper to darcs internals, not to talk from a pure Haskell solution. So, IMHO, resources spent on making some operation fly (using some indexing in the metadata?) are surely better rewarded than having a programmatical API to darcs operations. just my 0.1 euro, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. [EMAIL PROTECTED] | -- Fortunato Depero, 1929. _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
