On Wed, Aug 27, 2008 at 10:20 PM, David Bremner [EMAIL PROTECTED] wrote:
Ketil Malde wrote:
Another Debian question, once I've populated the debian/ directory one
way or another, how should this be integrated with the rest of the
project? Should it be part of the darcs archive, or a separate
Jason Dagit [EMAIL PROTECTED] writes:
2) Compile GHC yourself.
I find with Debian this is the way to go.
Ouch. Okay, I've compiled GHC once. But I would like end-users to be
able to use my software, and I simply cannot require them to go
through this.
Install your system and use Debian's
On Wed, Aug 27, 2008 at 1:58 AM, Jason Dagit [EMAIL PROTECTED] wrote:
2) Compile GHC yourself. You can even compile and install GHC (and most
Haskell software) on a dedicated user account. In this way you avoid
messing up you Debian installation if something goes wrong.
I find with Debian
2008/8/25 Ketil Malde [EMAIL PROTECTED]:
1. Etch comes with ghc-6.6, and that didn't work with my .cabal file.
Is it not an option to make your software work with the
not-quite-latest compiler? 6.8 is less than a year old, so I imagine
6.6 is still in quite a few major distro's stable
David House [EMAIL PROTECTED] writes:
1. Etch comes with ghc-6.6, and that didn't work with my .cabal file.
Is it not an option to make your software work with the
not-quite-latest compiler?
Yes it is, although I don't have the details either.
Neither do I have an Etch system around, but
Ketil Malde wrote:
Neither do I have an Etch system around, but I should probably
install a virtual machine or something. Ideally, I should
work out the minimal requirements (including for dependencies, and for
dependencies' dependencies), but in practice, I end up depending on
whatever is
ketil:
Jason Dagit [EMAIL PROTECTED] writes:
2) Compile GHC yourself.
I find with Debian this is the way to go.
Ouch. Okay, I've compiled GHC once. But I would like end-users to be
able to use my software, and I simply cannot require them to go
through this.
Yes, scary and
Ketil Malde wrote:
Another Debian question, once I've populated the debian/ directory one
way or another, how should this be integrated with the rest of the
project? Should it be part of the darcs archive, or a separate
archive (foo-debian), or what? How do people organize this?
[EMAIL
On Mon, Aug 25, 2008 at 9:10 AM, Mads Lindstrøm
[EMAIL PROTECTED] wrote:
Hi
Ketil Malde wrote:
I've had an interested user, who tried to get one of my programs to
run on a Debian machine - running Debian Etch, released a couple of
months ago. Here are some of the hurdles stumbled upon in
I've had an interested user, who tried to get one of my programs to
run on a Debian machine - running Debian Etch, released a couple of
months ago. Here are some of the hurdles stumbled upon in the
process:
1. Etch comes with ghc-6.6, and that didn't work with my .cabal file.
2. ghc-6.8.3,
Ketil Malde wrote:
I've had an interested user, who tried to get one of my programs to
run on a Debian machine - running Debian Etch, released a couple of
months ago.
Your user is pretty much at the pessimal point in the release cycle.
Etch is more than a year old, and lenny (the next
Hi
Ketil Malde wrote:
I've had an interested user, who tried to get one of my programs to
run on a Debian machine - running Debian Etch, released a couple of
months ago. Here are some of the hurdles stumbled upon in the
process:
Debian Etch were released in April 8th, 2007. 16 months ago.
12 matches
Mail list logo
