On Mon, 30 Oct 2006, David House wrote:
On 30/10/06, Tony Morris [EMAIL PROTECTED] wrote:
4) If you want links to base libraries in your haddock output, do such
and such (how do you do that anyway?)
I believe you need a local copy of the library sources, whose path you
give to haddock
[EMAIL PROTECTED] (Donald Bruce Stewart) writes:
But we could do with more information on:
[...]
How to make cabal projects into distribution-specific (.deb, .rpm, and
so on) packages?
-k
--
If I haven't seen further, it is by standing in the footprints of giants
Ketil Malde wrote:
How to make cabal projects into distribution-specific (.deb, .rpm, and
so on) packages?
The answer for .debs is: ask a Debian developer (or a prospective
developer) to package it for you.
The reason is that to make a good .deb, one needs to be familiar with a lot
of
On Mon, Oct 30, 2006 at 09:54:08AM +0100, Ketil Malde wrote:
How to make cabal projects into distribution-specific (.deb, .rpm, and
so on) packages?
for slackware you can have a look to this slackBuild script:
http://gorgias.mine.nu/repos/slackBuild/hxt/hxt/hxt.SlackBuild
regards,
andrea
On 30/10/06, Tony Morris [EMAIL PROTECTED] wrote:
4) If you want links to base libraries in your haddock output, do such
and such (how do you do that anyway?)
I believe you need a local copy of the library sources, whose path you
give to haddock with some flag.
--
-David House, [EMAIL
Hello Tony,
Monday, October 30, 2006, 6:22:31 AM, you wrote:
My suggestion:
The steps of reasoning as you start with a blank directory.
For example:
great idea! i'm sure that such sort of manual will be very helpful for
anyone starting his first haskell project
--
Best regards,
Bulat
There's been a bit of discussion on irc, lists and privately about
about documenting publically the best practice for creating a new
Haskell project -- be that a library or an application.
Some advice is now available here:
http://haskell.org/haskellwiki/How_to_write_a_Haskell_program
Tony Morris
http://tmorris.net/
Donald Bruce Stewart wrote:
There's been a bit of discussion on irc, lists and privately about
about documenting publically the best practice for creating a new
Haskell project -- be that a library or an application.
Agreed.
Some advice is now available
