cvs commit: fptools/libraries/Cabal/Distribution Make.hs Simple.hs fptools/libraries/Cabal/Distribution/Simple Utils.hs

[Isaac Jones]

Ross Paterson <ross at soi.city.ac.uk> writes:

> On Sun, Jan 09, 2005 at 04:22:34PM -0800, Isaac Jones wrote:
>> ijones      2005/01/09 16:22:34 PST
>> 
>>   Modified files:
>>     libraries/Cabal/Distribution Make.hs Simple.hs 
>>     libraries/Cabal/Distribution/Simple Utils.hs 
>>   Log:
>>   INTERFACE CHANGE: moved Setup.description to <pkgname>.cabal
>>   Now it searhes for *.cabal in the current directory, if it finds more
>>   than one, there's an error.  For now, it allows Setup.description with
>>   a warning.
>>   
>>   We can use <pkgname>.hsproj if someone doesn't like the .cabal name.
>
> Well, .cabal is a bit obscure.

The reason for .cabal is that there are a lot of different "packages"
running around.  Just to build one library for one compiler on one OS,
we have GHC packages, debian binary packages (for each arch), debian
source packages, and cabal packages.  I wanted something to make it
clear what the description file belongs to.  Setup.description tied it
to the Setup.lhs file, but foo.hspkg kinda orphans it a bit.  Hence
foo.cabal to clearly tie it to the cabal.

> What shall be have instead of Setup.buildinfo?
> (<pkgname>.caballero?)

Since the "buildinfo" is for somewhat more advanced users, I'm not as
worried about basic confusions; "<pkgname>.buildinfo" is fine by me.
Any suggestions?


peace,

  isaac