hackage-diff against latest version on hackage

[stepcut]

I discovered this package by accident because I named a similar tool I am working on hackage-diff.

The specific problem I was trying to solve with my tool is to be able to run a command in a project directory and figure out if what is in that directory is the same as the latest version of the package on hackage. If not, it means I probably need to upload a new version to hackage. I maintain a lot of packages, and often when a new version of text, etc, comes out I have to make mods to many, but not all of the packages. But, by the time I am done making the mods, building them in the continuous integration server, etc, I've long forgotten which packages I modified and need to upload. :)

Your tool seems to have a lot of extra, useful features that would be helpful for assigning a new version number, etc. But, it seems to require that you specify an exact version number for the package to compare against on hackage.

Do you think it is reasonable that we could merge our tools into a single unified tool?

I have uploaded my work in progress here:

https://github.com/stepcut/hackage-whatsnew

[blitzcode]

Hey, sorry for the super late reply. I just recently started fixing up some of my published Haskell projects again.

I don't really want to add any textual diff to this tool. It's really supposed to be about comparing actually exported functions and types, the actual API. I report breaking changes so Hackage authors know when to bump the version number. It's probably a good idea to have a feature where a local Hoogle DB is compared to the latest version on Hackage. It's probably the most common use case.

Right now, hackage-diff is a bit in a broken state because the Hoogle DB format has apparently changed. I just submitted some fixes for the biggest showstoppers, but there's some more work to be done. I haven't really looked into this, but with the Hoogle 5 rewrite I might wait for things to settle down a bit before I put any more work into this tool.