- cabal-devel - Haskell.org

Is it possible to link a haskell library directly with an external static C library(.a)?
by crocket 26 Oct '16

26 Oct '16

It seems that it is not possible to do so at this moment. https://github.com/jakubfijalkowski/hlibsass#static-shared-or-external-vers… explains the problem with not being able to do so. Is there a plan to make cabal link a haskell library directly with an external static C library?

1 0

Fwd: GHC 8.0.2 status
by Edward Z. Yang 10 Oct '16

10 Oct '16

If we want a bugfix version of Cabal in with GHC 8.0.2 this is our last chance. --- Begin forwarded message from Ben Gamari --- From: Ben Gamari <ben(a)well-typed.com> To: Gabor Greif <ggreif(a)gmail.com>, Pali Gabor Janos <pali.gabor(a)gmail.com>, Gershom B <gershomb(a)gmail.com>, Jens Petersen <juhpetersen(a)gmail.com>, "\"Erik Rantapaa\"" <erantapaa(a)gmail.com>, Erik de Casto Lopo <erikd(a)mega-nerd.com>, Randy Polen <randyhaskell(a)outlook.com>, Karel Gardas <karel.gardas(a)centrum.cz>, Herbert Valerio Riedel <hvriedel(a)gmail.com> Cc: GHC developers <ghc-devs(a)haskell.org> Date: Mon, 10 Oct 2016 10:42:51 -0400 Subject: GHC 8.0.2 status Hello GHCers, Thanks to the work of darchon the last blocker for the 8.0.2 release (#12479) has nearly been resolved. After the fix has been merged I'll be doing some further testing of the ghc-8.0 branch and cut a source tarball for 8.0.2-rc1 later this week. If you intend on offering a binary release for 8.0.2 it would be great if you could plan on testing the tarball promptly so we can cut 8.0.2 and move on to planning for 8.2.1. Thanks for your help and patience! Cheers, - Ben --- End forwarded message ---

2 1

Hackathon 2016 Wiki page
by Mikhail Glushenkov 07 Oct '16

07 Oct '16

Hi *, I started writing a Wiki page with a list of ideas for this weekend's HaskellX hackathon in London. Please feel free to expand and improve: https://github.com/haskell/cabal/wiki/Hackathon-2016

1 0

cabal new-* commands awesomeness
by Ramakrishnan Muthukrishnan 19 Sep '16

19 Sep '16

I just wanted to say, `cabal new-configure' and `new-install' commands are awesome! Thanks to everyone who worked on it. I have a few (unrelated) questions: 1. Will the `new' variants become the default? That will be nice! 2. I would like to contribute to Cabal project (especially after the recent "discussions" on reddit and elsewhere on cabal vs stack etc..). Are there "byte-sized" projects for people unfamiliar with Cabal source code to look at? I saw that some bugs are tagged as "easy". Starting to take a look. 3. Is there an irc channel where cabal devs hang out? Thanks -- Ramakrishnan

2 1

building a project with new-* commands
by Ramakrishnan Muthukrishnan 16 Sep '16

16 Sep '16

I have a fairly simple hakyll based blog website that I usually build with cabal sandbox. Today I tried the new-configure/new-build commands. It built a bunch of dependencies but the dist/build directory is empty. It doesn't look like it built the project itself. Subsequent builds are fast as expected. But I still don't see anything in dist/build directory. Am I missing something or doing something silly? Not sure if this is the right list to discuss "user" issues as this is a "devel" list. I created a new project with `cabal init' and built it with the new style commands and it produced an executable in the expected place. The cabal-install/Cabal version I am running is 1.24.0.0 (for both) with GHC 8.0.1 on Debian GNU/Linux x86-64. Thanks -- Ramakrishnan

3 5

New milestones for Cabal
by Edward Z. Yang 06 Sep '16

06 Sep '16

I've been trying to do triage on the bugtracker, and I've been pretty unhappy with the old milestone system. So I tried something new: - No more separate Cabal/cabal-install milestones. We're tightly coupled, and if we do uncouple, then we can talk separate, but not while the projects live in the same repo. - Replaced the point and feature milestones with "Soon" and "Later". Soon = release manager (Mikhail) wants this ticket fixed in a patch release. I think this is how milestones were currently being used in a useful manner today, so this basically should stay unchanged. Only the RM gets to make decisions about what should happen soon. Later = some developer is planning to try to get this feature in to the next release cycle. They're actively working on it, we can bug them when release time comes around for them to finish it up. So this is NOT a bin where you just put things you'd like to see in the next release. Either someone *is* working on it, or developers have agreed (e.g., via triage meeting/discussion) that this feature is a priority for the next release - I introduced a "Triaged" category for bugs which have repro'd test cases and just need someone to take care of them. The idea is that if you feel like doing some bug hunting, just look for something in Triaged and fix it. Not sure if this will work, giving it a try. - Everything else should be marked as Never. That doesn't mean it won't happen, just that someone needs to specifically step up to make it happen. I added a special subcategory for "Obsoleted by Nix build", since many bugs are in legacy code which won't manifest with the new-build path. So, hope that helps turn the milestone system into something a bit more useful.

1 0

Opening up Cabal development
by Edward Z. Yang 17 Jul '16

17 Jul '16

6 11

I reorged labels on Cabal's GitHub
by Edward Z. Yang 12 Jul '16

12 Jul '16

If you hate it I can change it back but give it a try for now. If the "component" prefix in "component: solver" is too long we could go for something like "C-solver" but I think that is less transparent. I also added some new labels, "paging: ezyang (...)". In the parenthetical should be a quick summary of the types of things you are interested in getting paged for. I tried to guess some but I am not perfect, please feel free to change your description / add a label for yourself (I didn't get everyone) / tell me how you want yours changed. Edward

4 11

Re: [Haskell] The Haddock documentation is not showing up on the Hackage
by Henning Thielemann 27 Jun '16

27 Jun '16

On Mon, 27 Jun 2016, KwangYul Seo wrote: > I uploaded a package named enchant on the Hackage last week, but the > Haddock documentation is not showing up yet. The Status field says "Docs > pending" and "Build status unknown". This is certainly not for haskell(a)haskell.org. I am answering to haskell-cafe and cabal-devel. > https://hackage.haskell.org/package/enchant-0.1.0.0 > > enchant uses c2hs as a build tool to generate the FFI binding and > requires libenchant-dev to be installed on the machine. I wonder how I > can tell these build requirements to the Hackage server. I assume that it is not a good idea to install many additional packages on the Haskell server. Thus I think the best you can do is to upload the documentation yourself via the package maintenance site. Here is a script that should help creating the docs locally and upload them to Hackage: https://raw.githubusercontent.com/ekmett/lens/master/scripts/hackage-docs.sh

3 3

[ANN] Cabal and cabal-install 1.24.0.0 have been released
by Ryan Thomas 11 May '16

11 May '16

Hi all, Cabal and cabal-install 1.24.0.0 have been released. These have been uploaded to hackage, tagged in the repo and updated on the downloads page. The changelog is quite extensive, so please see here <https://github.com/haskell/cabal/blob/1.24/cabal-install/changelog> and here <https://github.com/haskell/cabal/blob/1.24/Cabal/changelog> for the complete details. Cheers, ryan

2 1