Proposal: store updates to package descriptions with Git as backend about hackage-server HOT 4 CLOSED

The right thing to do is to make all the revisions available via its general REST api and then anyone can mirror those wherever they like.

But doing the git thing directly is not something we plan to integrate into the server. The general design is to make all information available via the REST interface.

from hackage-server.

The general design is to make all information available via the REST interface.

So I see it's possible to

1. use the current backend
2. implement (within Hackage) the REST interface, which I agree is needed anyway
3. (even externally) implement a mirror to a git repo, as long as the load is not excessive (which hopefully is not a problem).

I agree you need a web frontend, but I think my proposal is not in conflict. I wonder what "all information" means: the core is a persistent map from packages and ids to cabal files, but will I (eventually) be able to look on Hackage at changes to those files among two snapshots of the map?

I suspected that using Git (or maybe other VCSs) as a backend would save effort anyway, because you can use it to implement efficiently the persistent map I mentioned above (encoding packages and ids as filenames) - and for instance with Git you get delta compression for free. By choosing that backend, one gets also everything else for free - like for instance for Homebrew (which might depend even more on Git, but that's not my point).

from hackage-server.

Anyway, feel free to close the issue if you believe the idea isn't worthwhile.

from hackage-server.

Yes, all the info should be available so that you or anyone could mirror the info into a git repo.

Currently the thing that is not available is the revisions, but that should be easy to fix, and we'd be happy to accept patches to do that.

from hackage-server.