<p><br>
On Feb 4, 2013 8:43 AM, "Ian Lynagh" <<a href="mailto:ian@well-typed.com">ian@well-typed.com</a>> wrote:<br>
><br>
> On Sun, Feb 03, 2013 at 08:48:13PM +0000, Simon Marlow wrote:<br>
> > On 02/02/13 14:11, Ian Lynagh wrote:<br>
> > ><br>
> > >>diff --git a/unix.cabal b/unix.cabal<br>
> > >>index 287caa8..1aaaec9 100644<br>
> > >>--- a/unix.cabal<br>
> > >>+++ b/unix.cabal<br>
> > >>@@ -14,6 +14,11 @@ description:<br>
> > >> IEEE Std. 1003.1).<br>
> > >> .<br>
> > >> The package is not supported under Windows (except under Cygwin).<br>
> > >>+ .<br>
> > >>+ Changes in <a href="http://2.7.0.0">2.7.0.0</a>:<br>
> > >>+ .<br>
> > >>+ * @ProcessStatus@ changed to include a core-dumped flag.<br>
> > >>+<br>
> > >> extra-source-files:<br>
> > >> config.guess config.sub install-sh<br>
> > >> <a href="http://configure.ac">configure.ac</a> configure<br>
> > ><br>
> ><br>
> > >Also, what's the plan for the changelog? Is the package description<br>
> > >going to accumulate entries, or just show those for the most recent<br>
> > >version? Wouldn't it be better to include a CHANGES file instead?<br>
> ><br>
> > I've got into the habit of putting change notes in the description<br>
> > field of the .cabal file, because they appear prominently in the<br>
> > Haddock docs, whereas a CHANGES file or similar is hard to find and<br>
> > tends to get forgotten (at least I tend to forget it).<br>
> ><br>
> > I don't have a specific rule for the number of versions to keep, but<br>
> > I suppose you wouldn't want the list to get too long.<br>
><br>
> Hmm. I think it would be better to have Cabal/haddock understand a<br>
> CHANGES file in a particular format. That way haddock (and hackage)<br>
> could show the recent changes on a package's page, with a link to the<br>
> full history, and the description can remain just a description of what<br>
> the package does.</p>
<p>Or even just a link to the raw text file on Hackage.</p>
<p>><br>
><br>
> Thanks<br>
> Ian<br>
><br>
><br>
> _______________________________________________<br>
> Libraries mailing list<br>
> <a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/libraries">http://www.haskell.org/mailman/listinfo/libraries</a><br>
</p>