Hi, I'm just starting learning Haskell (went through a couple of tutorials and wrote simple examples), and I'm looking for a project to help out with. I've been pointed at recent Duncan's request for help - let me know what problems (simple for now) I can work on (Easy Tickets?). Thanks, Simon
On Sun, 2007-08-12 at 20:09 +0100, Simon (Vsevolod) Ilyushchenko wrote:
Hi,
I'm just starting learning Haskell (went through a couple of tutorials and wrote simple examples), and I'm looking for a project to help out with. I've been pointed at recent Duncan's request for help - let me know what problems (simple for now) I can work on (Easy Tickets?).
Our big list of tickets is here: (defects grouped by priority) http://hackage.haskell.org/trac/hackage/query?status=new&status=assigned&status=reopened&group=priority&type=defect&order=priority We're coming up to a release and one thing we'll need to do is make sure all the commands and flags are fully documented in the user guide. This would involve modifying the doc/Cabal.xml docbook file: http://hackage.haskell.org/trac/hackage/ticket/109 Making sure cabal-install compiles with the latest version of Cabal is a priority and should be fairly easy, there have been some api changes. Then it's a matter of testing and seeing what still needs improving. darcs get --partial http://darcs.haskell.org/cabal darcs get --partial http://darcs.haskell.org/cabal-install Duncan
Got it, thanks.
Is there a time when I can hang out on #haskell (or other channel) to
get some questions answered? For example, when trying to install cabal
itself, running
ghc -v --make Setup.lhs -o setup
currently fails for me with:
Could not find module `System.FilePath':
locations searched:
System/FilePath.hs
System/FilePath.lhs
(imported from ./Distribution/Simple.hs)
I'm running ghc 6.4.2 - I've found some hints that I should use 6.6.1,
but I'm not quite sure of it.
Thanks,
Simon
On 8/12/07, Duncan Coutts
On Sun, 2007-08-12 at 20:09 +0100, Simon (Vsevolod) Ilyushchenko wrote:
Hi,
I'm just starting learning Haskell (went through a couple of tutorials and wrote simple examples), and I'm looking for a project to help out with. I've been pointed at recent Duncan's request for help - let me know what problems (simple for now) I can work on (Easy Tickets?).
Our big list of tickets is here: (defects grouped by priority)
We're coming up to a release and one thing we'll need to do is make sure all the commands and flags are fully documented in the user guide. This would involve modifying the doc/Cabal.xml docbook file:
http://hackage.haskell.org/trac/hackage/ticket/109
Making sure cabal-install compiles with the latest version of Cabal is a priority and should be fairly easy, there have been some api changes. Then it's a matter of testing and seeing what still needs improving.
darcs get --partial http://darcs.haskell.org/cabal darcs get --partial http://darcs.haskell.org/cabal-install
Duncan
On Mon, Aug 13, 2007 at 12:10:42AM +0100, Simon (Vsevolod) Ilyushchenko wrote:
Got it, thanks.
Is there a time when I can hang out on #haskell (or other channel) to get some questions answered? For example, when trying to install cabal itself, running
ghc -v --make Setup.lhs -o setup currently fails for me with:
Could not find module `System.FilePath': locations searched: System/FilePath.hs System/FilePath.lhs (imported from ./Distribution/Simple.hs)
I'm running ghc 6.4.2 - I've found some hints that I should use 6.6.1, but I'm not quite sure of it.
#haskell is usually pretty active. Newbies have an odd tendancy to show up precisely at our rare dead times, but I assure you that right now (Aug 12 23:16 UTC) we're active. Stefan (sorear)
On Mon, 2007-08-13 at 00:10 +0100, Simon (Vsevolod) Ilyushchenko wrote:
Got it, thanks.
Is there a time when I can hang out on #haskell (or other channel) to get some questions answered? For example, when trying to install cabal itself, running
ghc -v --make Setup.lhs -o setup currently fails for me with:
ghc-6.4 should be fine but yes you do need the filepath package. You can get that from hackage.haskell.org. When bootstrapping a new version of cabal, using "make setup" is the simplest thing. That creates a ./setup program which you can use to run the normal cabal commands like ./setup configure; ./setup build; ./setup install What I normally do when hacking on Cabal is to: ./setup register --user --inplace That registers the development version of Cabal inplace, in the actual build tree, so that means from then on, using the Cabal package means using whatever you've currently got compiled in your local build tree. Then using ./setup build updates the already registered Cabal-1.1.7 without having to reinstall or re-register. That's handy if one is testing building other packages with the development version of Cabal interleaved with making changes to Cabal. So bear in mind that if you ./setup clean for example then you'll not be breaking your registered Cabal-1.1.7 and you'' be unable to compile anything against -package Cabal-1.1.7 until you ./setup build again. That's not such a problem however since you can always specify using an older version when building other things like -package Cabal-1.1.6. Duncan
Hi,
ghc-6.4 should be fine but yes you do need the filepath package. You can get that from hackage.haskell.org.
When bootstrapping a new version of cabal, using "make setup" is the simplest thing. That creates a ./setup program which you can use to run the normal cabal commands like ./setup configure; ./setup build; ./setup install
What I normally do when hacking on Cabal is to:
./setup register --user --inplace
Installing any packages with --user option leads to error messages about missing /home/user/.ghc/i386-linux-6.4.2/package.conf
That registers the development version of Cabal inplace, in the actual build tree, so that means from then on, using the Cabal package means using whatever you've currently got compiled in your local build tree.
Then using
./setup build
updates the already registered Cabal-1.1.7 without having to reinstall or re-register. That's handy if one is testing building other packages with the development version of Cabal interleaved with making changes to Cabal.
So bear in mind that if you ./setup clean for example then you'll not be breaking your registered Cabal-1.1.7 and you'' be unable to compile anything against -package Cabal-1.1.7 until you ./setup build again. That's not such a problem however since you can always specify using an older version when building other things like -package Cabal-1.1.6.
As for trying to install the latest cabal-install with the latest cabal (registered globally), I get this error: Setup.lhs: cabal-install.cabal:12: Unknown field 'build-type' The Build-type field is present in the checked-out tree, so presumably I'm still using the old Cabal somehow. I can hang out at #haskell today.
On 8/19/07, Simon (Vsevolod) Ilyushchenko
Hi,
ghc-6.4 should be fine but yes you do need the filepath package. You can get that from hackage.haskell.org.
When bootstrapping a new version of cabal, using "make setup" is the simplest thing. That creates a ./setup program which you can use to run the normal cabal commands like ./setup configure; ./setup build; ./setup install
What I normally do when hacking on Cabal is to:
./setup register --user --inplace
Installing any packages with --user option leads to error messages about missing /home/user/.ghc/i386-linux-6.4.2/package.conf
That registers the development version of Cabal inplace, in the actual build tree, so that means from then on, using the Cabal package means using whatever you've currently got compiled in your local build tree.
Then using
./setup build
updates the already registered Cabal-1.1.7 without having to reinstall or re-register. That's handy if one is testing building other packages with the development version of Cabal interleaved with making changes to Cabal.
So bear in mind that if you ./setup clean for example then you'll not be breaking your registered Cabal-1.1.7 and you'' be unable to compile anything against -package Cabal-1.1.7 until you ./setup build again. That's not such a problem however since you can always specify using an older version when building other things like -package Cabal-1.1.6.
As for trying to install the latest cabal-install with the latest cabal (registered globally), I get this error: Setup.lhs: cabal-install.cabal:12: Unknown field 'build-type'
The Build-type field is present in the checked-out tree, so presumably I'm still using the old Cabal somehow.
I can hang out at #haskell today.
ping? Anyone on #haskell now?
On Sun, Aug 26, 2007 at 01:19:27PM -0700, Stefan O'Rear wrote:
On Sun, Aug 26, 2007 at 08:57:47PM +0100, Simon (Vsevolod) Ilyushchenko wrote:
ping? Anyone on #haskell now?
Yes, a solid 384 people, including myself. (irc.freenode.net)
To be more specific, what leads people like you and Andrew Coppin to think the channel is dead? I've never seen evidence of that from inside, and we might need to fix what you're seeing... Stefan
Hi
To be more specific, what leads people like you and Andrew Coppin to think the channel is dead? I've never seen evidence of that from inside, and we might need to fix what you're seeing...
At some times of day/week there is relatively little chatter on the channel. That usually means people are hard at coding though, and there are usually plenty of people hanging around. If you want to ask a particular question to which there is a low level of expertise on the channel - Windows related for example - it is quite possible that no one will hear your particular question and be able to answer. I don't think the channel is dead (far from it!), but it isn't always an oracle to answer all questions at all times. Thanks Neil
participants (4)
-
Duncan Coutts -
Neil Mitchell -
Simon (Vsevolod) Ilyushchenko -
Stefan O'Rear