Cabal hack night suggestions
johan.tibell at gmail.com
Mon Jan 6 12:53:43 UTC 2014
Great to here that you're going to hack on cabal. We need all the
contributors we can get!
The general roadmap for 1.20 is here:
The "Do the right thing automatically" section is probably the most newbie
Other than that we really need to get the bug tracker under control. This
means triaging bugs and fixing those that need fixing and closing the rest.
I took a stab at this a while ago but if you want something to get your
feet wet, I suggest grabbing something that looks interesting from the bug
As for hacking on cabal, I suggest using sandboxes, like so:
# only once:
cabal sandbox init
cabal sandbox add-source ../Cabal
cabal install -j --only-dep
# to (re)build:
On Fri, Jan 3, 2014 at 1:50 PM, David Laing <dave.laing.80 at gmail.com> wrote:
> Hi all,
> There are a few people in my local FP meetup group looking into doing some
> semi-regular Haskell hack nights, and we're hoping to target various tools
> and libraries in the Haskell ecosystem so that we can give back a little
> while having fun and honing our skills.
> Cabal is pretty high on our list of things to hack on, and we're hoping to
> start mid next week.
> I'm sure we'll be able to click through github issues and submit pull
> requests on our own, but I thought I'd ask if anyone has any thoughts on
> areas that would be good to look at that might sit in a sweet spot of being
> both beneficial to Cabal and accessible to newcomers to the code.
> Does anyone have any thoughts?
> cabal-devel mailing list
> cabal-devel at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cabal-devel