darcs support for ohloh

[simonmichael]

This is Neil Mayhew's recent update of my three year old darcs support patches, cf https://github.com/simonmichael/ohloh_scm/pull/1 .

[lowfatcomputing]

Any response to this from @blackducksw?

I would very much like to see darcs support in openhub (because many of my projects use darcs), and it looks like there are people willing to maintain this.

[neilmayhew]

@lowfatcomputing I've heard nothing, which is very disappointing. Doubly-disappointing because "This pull request contains merge conflicts that must be resolved." I put in some work originally, to get it rebased onto the tip of master, hoping this would make it easy for someone to review and merge it. If you could lobby for this that would be very helpful, as I'm tied up with family issues at the moment.

Come on, @blackducksoftware, how about it?

[PDegenPortnoy]

Gentlemen; I apologize for the utter lack of response for your efforts.

I've merged the PR source, simonmichael/ohloh_scm into a branch in my local VM and resolved the merge conflicts. However, I ran into some issues running the tests. First, heheh, I needed to install darcs.

To do this I did the following:

$ sudo apt-get install haskell-platform
$ cabal update
$ sudo apt-get isntall libncurses5-dev
$ sudo apt-get install libcurl4-openssl-dev
$ cabal install terminfo-0.3.2.6
$ cabal install darcs

When all this still failed to produce an executable "darcs", I downloaded the binary, unarchived it and put it into a bin directory on my path. All that done, I ran "rake" and got many, many failures.

And having done all that last night, this morning we made some sizable changes to the code base in order to publish the library as a gem.

I will continue tapping on the branch I've created to get it updated from the latest master and resolve the test failures -- they are undefined names, so very likely some missing require statement -- and then push the branch up to this repository for your thoughts.

[simonmichael]

Thanks Peter!
apt-get install darcs gets you a still-new-enough darcs, FYI.

[PDegenPortnoy]

Thank you Simon; I'll add that to my notes so we can have a reproducible production installation process.

[PDegenPortnoy]

@simonmichael, @lowfatcomputing, @neilmayhew: May I ask that you look at the darcs_support branch? I've resolved the merge and namespacing issues. There are 5 failing tests that I've only cursorily looked at. Some of them seem to be looking for some configuration value: "Each patch is attributed to its author, usually by email address..."

Once we get these resolved, it would seem that we complete this process.

[marclaporte]

bump :-)

[neilmayhew]

@peterdp: I'm sorry for the lack of response on this. I'm not a darcs user myself, so someone else needs to test this. I was just helping out with resolving the git conflicts.

It looks like this PR has been superseded by #23 so maybe it should be closed, especially since it now has conflicts. @simonmichael, how do you feel about that?

[simonmichael]

If so, fine with me - thanks.

[PDegenPortnoy]

Closing PR as it's been superseded by #23