cvs commit: fptools/libraries/Cabal/doc Cabal.xml Makefile
ijones at syntaxpolice.org
Wed Feb 9 12:12:48 EST 2005
> On 09 February 2005 12:12, Ross Paterson wrote:
>> ross 2005/02/09 04:12:06 PST
>> Added files:
>> libraries/Cabal/doc Cabal.xml Makefile
>> first attempt at a User's Guide. Somewhat terse, with a Unix bias,
>> and the last section is empty. Feel free to fix, and please reflect
>> interface changes here.
Cool :) I can't wait to look at this. I'll probably be dumping more
and more cycles into the documentation as we run out of high priority
hacking to do.
"Simon Marlow" <simonmar at microsoft.com> writes:
> Good stuff. Does anyone have any bright ideas about how we should
> provide the runhaskell program?
For runhaskell to be useful, it should probably end up in a pretty
standard place, either /usr/bin or /usr/local/bin, and it will
therefore be pretty easy to figure out if it's installed.
So I think that it should come with all compilers, but they should go
check if it exists yet. If it does, leave it alone, but install
runFoo for your compiler. If it doesn't exist, then install runFoo
and link runhaskell to runFoo.
For Debian, we have an alternatives system for things like this, so
it'll probably be handled in the packaging system unless we have a
brilliant solution here; I suppose RPM has something similar.
At first, it could just be a symbolic link to either runhugs or
runghc. Later we could get more fancy and add the idea of a default
compiler and such like in hmake.
Not too "bright", but that's the best I could come up with.
More information about the Cvs-libraries