All this work on Cabal is great! Can I just emit one plea, namely that we don't forget to write a separate, comprehensible, standalone document describing Cabal and how to use it. The "proposal" document is an excellent starting point but (a) the design has changed a bit, (b) the proposal discussed design choices that are now fixed, (c) we could probably do with "how-to" chapters for Angela Author and perhaps other personae. The Haddock for the source code isn't enough! So far as getting Cabal used, documenting it is extremely important. Simon | -----Original Message----- | From: libraries-bounces@haskell.org [mailto:libraries-bounces@haskell.org] On Behalf Of Isaac Jones | Sent: 04 January 2005 19:11 | To: Simon Marlow | Cc: libraries@haskell.org; Ross Paterson | Subject: Re: package description files | | "Simon Marlow" writes: | | > On 04 January 2005 15:39, Ross Paterson wrote: | > | >> On Tue, Jan 04, 2005 at 03:31:44PM -0000, Simon Marlow wrote: | >>> On 04 January 2005 10:36, Ross Paterson wrote: | >>> | >>>> I'd like to second Krasimir's suggestion that package description | >>>> files be called Package.description (or package.description), which | >>>> seems obviously more appropriate than Setup.description. In | >>>> addition, these files will be used by other tools as well as Cabal | >>>> setup scripts.