It would be nice if Hackage displayed ``recent changes'' of a package. [severity: wishlist] You see, I am subscribed to the ``hackage - recent additions'' feed [http://hackage.haskell.org/packages/archive/recent.rss] and receive entries that look like this: Cabal 1.8.0.2 Added by DuncanCoutts, Wed Dec 16 04:19:24 UTC 2009. A framework for packaging Haskell software This is sweet. But how can I tell what's new in Cabal since 1.6.0.3? (`Cabal' is just an example here.) * * * -- these are snowflakes Dear Santa, This year, I have been a very good boy (in his thirties). I have not pillaged, and I have often helped my children with their homework. And I always say `thank you', which makes me polite and so I deserve lots of presents this year! Please bring this stuff for me and the people in Haskell community. -- vvv
On Wed, Dec 16, 2009 at 10:18 AM, Valery V. Vorotyntsev
It would be nice if Hackage displayed ``recent changes'' of a package.
Yes I wish for this too. These are the hackage tickets on this: "Add Changelog summary feature to sdist" http://hackage.haskell.org/trac/hackage/ticket/244 "Add changelog feature to hackagedb" http://hackage.haskell.org/trac/hackage/ticket/299 Bas
On Wed, 2009-12-16 at 11:18 +0200, Valery V. Vorotyntsev wrote:
It would be nice if Hackage displayed ``recent changes'' of a package. [severity: wishlist]
You see, I am subscribed to the ``hackage - recent additions'' feed [http://hackage.haskell.org/packages/archive/recent.rss] and receive entries that look like this:
Cabal 1.8.0.2 Added by DuncanCoutts, Wed Dec 16 04:19:24 UTC 2009. A framework for packaging Haskell software
This is sweet. But how can I tell what's new in Cabal since 1.6.0.3? (`Cabal' is just an example here.)
Yep it's a fair point. http://hackage.haskell.org/trac/hackage/ticket/299 Some packages have a changelog file in them that we could display, though most don't. For those that do have a changelog, how we avoid displaying all of history is a bit tricky. For those that do not, ideally we could derive a changelog by looking at the difference in the API. The latter requires a tool we've not written yet. Duncan
Am Mittwoch 16 Dezember 2009 14:45:18 schrieb Duncan Coutts:
On Wed, 2009-12-16 at 11:18 +0200, Valery V. Vorotyntsev wrote:
It would be nice if Hackage displayed ``recent changes'' of a package. [severity: wishlist]
You see, I am subscribed to the ``hackage - recent additions'' feed [http://hackage.haskell.org/packages/archive/recent.rss] and receive entries that look like this:
Cabal 1.8.0.2 Added by DuncanCoutts, Wed Dec 16 04:19:24 UTC 2009. A framework for packaging Haskell software
This is sweet. But how can I tell what's new in Cabal since 1.6.0.3? (`Cabal' is just an example here.)
Yep it's a fair point.
http://hackage.haskell.org/trac/hackage/ticket/299
Some packages have a changelog file in them that we could display, though most don't. For those that do have a changelog, how we avoid displaying all of history is a bit tricky. For those that do not, ideally we could derive a changelog by looking at the difference in the API. The latter requires a tool we've not written yet.
Duncan
How about two files, a changelog with the history and a "What's new in this release" which gets copied to the top of the changelog on the next release? It's only marginally more work for the author/maintainer of a package, I think, and would make the job for hackage much easier.
Valery V. Vorotyntsev wrote:
It would be nice if Hackage displayed ``recent changes'' of a package. [severity: wishlist]
You see, I am subscribed to the ``hackage - recent additions'' feed [http://hackage.haskell.org/packages/archive/recent.rss] and receive entries that look like this:
Cabal 1.8.0.2 Added by DuncanCoutts, Wed Dec 16 04:19:24 UTC 2009. A framework for packaging Haskell software
This is sweet. But how can I tell what's new in Cabal since 1.6.0.3? (`Cabal' is just an example here.)
Duncan Coutts
Yep it's a fair point.
http://hackage.haskell.org/trac/hackage/ticket/299
Some packages have a changelog file in them that we could display, though most don't. For those that do have a changelog, how we avoid displaying all of history is a bit tricky. For those that do not, ideally we could derive a changelog by looking at the difference in the API. The latter requires a tool we've not written yet.
We could mimic Debian's approach. Debian policy requires changelogs of standard format. [1] These changelogs are updated with debchange(1) tool and can be parsed with parsechangelog(1p). [2,3] See example. [4] [1] http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog [2] http://manpages.debian.net/cgi-bin/man.cgi?query=debchange [3] http://manpages.debian.net/cgi-bin/man.cgi?query=parsechangelog [4] http://packages.debian.org/changelogs/pool/main/x/xterm/current/changelog -- vvv
Some packages have a changelog file in them that we could display, though most don't.
Debian policy requires changelogs of standard format.
Most packages use a well known version control system (darcs, mercurial etc.). Cabal also has fields helping identifying where in vcs history are each version placed. Listing change history between them is something we can script. Personally I think, though, that changelog format should be part of Cabal package format documentation. Best, Maurício
participants (5)
-
Bas van Dijk -
Daniel Fischer -
Duncan Coutts -
Maurício CA -
Valery V. Vorotyntsev