From ezyang at mit.edu Tue Sep 6 10:32:20 2016 From: ezyang at mit.edu (Edward Z. Yang) Date: Tue, 06 Sep 2016 03:32:20 -0700 Subject: New milestones for Cabal Message-ID: <1473157113-sup-3943@sabre> 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. From ram at rkrishnan.org Fri Sep 16 11:40:45 2016 From: ram at rkrishnan.org (Ramakrishnan Muthukrishnan) Date: Fri, 16 Sep 2016 17:10:45 +0530 Subject: building a project with new-* commands Message-ID: <1474026045.452659.727694897.5FF204AE@webmail.messagingengine.com> 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 From lsp at informatik.uni-kiel.de Fri Sep 16 12:23:17 2016 From: lsp at informatik.uni-kiel.de (lennart spitzner) Date: Fri, 16 Sep 2016 14:23:17 +0200 Subject: building a project with new-* commands In-Reply-To: <1474026045.452659.727694897.5FF204AE@webmail.messagingengine.com> References: <1474026045.452659.727694897.5FF204AE@webmail.messagingengine.com> Message-ID: <1d65c06c-d999-a915-4ad9-b62e38172135@informatik.uni-kiel.de> The build artefacts of new-* are placed in a "dist-newstyle" directory. Another common mistake with 1.24.0.0 is that `cabal new-build` won't do much at all if run in some parent directory. You might need to `cabal new-build ./my-blog/` and then get the artefacts somewhere (burried) in ./my-blog/dist-newstyle/... (I believe there is some improvement regarding behaviour in the parent directory in master already; certainly was planned.) Hope that helps. -- lennart On 16/09/16 13:40, Ramakrishnan Muthukrishnan wrote: > 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 > From ram at rkrishnan.org Fri Sep 16 12:34:14 2016 From: ram at rkrishnan.org (Ramakrishnan Muthukrishnan) Date: Fri, 16 Sep 2016 18:04:14 +0530 Subject: building a project with new-* commands In-Reply-To: <1d65c06c-d999-a915-4ad9-b62e38172135@informatik.uni-kiel.de> References: <1474026045.452659.727694897.5FF204AE@webmail.messagingengine.com> <1d65c06c-d999-a915-4ad9-b62e38172135@informatik.uni-kiel.de> Message-ID: <1474029254.468796.727739425.6302C29B@webmail.messagingengine.com> Hi Lennart, Thanks for the email. Sorry, I wrongly wrote the path "dist" when I meant "dist-newstyle". When I created a fresh project, just doing `cabal new-build' created a binary. Here is what I get in my blog directory. ram at knuth:~/src/newblog$ cabal new-configure Resolving dependencies... In order, the following would be built (use -v for more details): zip-archive-0.3.0.5 pandoc-1.17.2 pandoc-citeproc-0.10.1 hakyll-4.8.3.2 rkrishnan-0.0.1 ram at knuth:~/src/newblog$ cabal new-build . In order, the following will be built (use -v for more details): zip-archive-0.3.0.5 pandoc-1.17.2 pandoc-citeproc-0.10.1 hakyll-4.8.3.2 rkrishnan-0.0.1 Configuring zip-archive-0.3.0.5... ram at knuth:~/src/newblog$ ls dist-newstyle/build/ ram at knuth:~/src/newblog$ cd .. ram at knuth:~/src$ cabal new-build ./new-blog/ BadPackageLocations [BadLocGlobEmptyMatch "./*.cabal"] I will try building and trying the `master' branch. Thanks again. Cheers Ramakrishnan On Fri, Sep 16, 2016, at 05:53 PM, lennart spitzner wrote: > The build artefacts of new-* are placed in a "dist-newstyle" directory. > > Another common mistake with 1.24.0.0 is that `cabal new-build` won't > do much at all if run in some parent directory. You might need to > `cabal new-build ./my-blog/` and then get the artefacts somewhere > (burried) in ./my-blog/dist-newstyle/... > > (I believe there is some improvement regarding behaviour in the parent > directory in master already; certainly was planned.) > > Hope that helps. > > -- lennart > > > On 16/09/16 13:40, Ramakrishnan Muthukrishnan wrote: > > 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 From hvriedel at gmail.com Fri Sep 16 12:38:17 2016 From: hvriedel at gmail.com (Herbert Valerio Riedel) Date: Fri, 16 Sep 2016 14:38:17 +0200 Subject: building a project with new-* commands In-Reply-To: <1474029254.468796.727739425.6302C29B@webmail.messagingengine.com> (Ramakrishnan Muthukrishnan's message of "Fri, 16 Sep 2016 18:04:14 +0530") References: <1474026045.452659.727694897.5FF204AE@webmail.messagingengine.com> <1d65c06c-d999-a915-4ad9-b62e38172135@informatik.uni-kiel.de> <1474029254.468796.727739425.6302C29B@webmail.messagingengine.com> Message-ID: <87intwaukm.fsf@gmail.com> Hi! On 2016-09-16 at 14:34:14 +0200, Ramakrishnan Muthukrishnan wrote: [..] > I will try building and trying the `master' branch. Thanks again. That's generally recommended with new-build at this point, since a lot of things have improved in cabal 1.25/master since cabal 1.24; Also, I'd also recommend consulting http://cabal.readthedocs.io/en/latest/nix-local-build-overview.html for the latest bleeding edge documentation from `master`; if you notice something that's unclear in the documentation, it's a documentation bug and you should either inform us about it, or maybe even provide a pull-request! Thanks From ram at rkrishnan.org Fri Sep 16 12:40:14 2016 From: ram at rkrishnan.org (Ramakrishnan Muthukrishnan) Date: Fri, 16 Sep 2016 18:10:14 +0530 Subject: building a project with new-* commands In-Reply-To: <87intwaukm.fsf@gmail.com> References: <1474026045.452659.727694897.5FF204AE@webmail.messagingengine.com> <1d65c06c-d999-a915-4ad9-b62e38172135@informatik.uni-kiel.de> <1474029254.468796.727739425.6302C29B@webmail.messagingengine.com> <87intwaukm.fsf@gmail.com> Message-ID: <1474029614.470204.727745217.2CD83DF2@webmail.messagingengine.com> On Fri, Sep 16, 2016, at 06:08 PM, Herbert Valerio Riedel wrote: > Hi! > > On 2016-09-16 at 14:34:14 +0200, Ramakrishnan Muthukrishnan wrote: > [..] > > > I will try building and trying the `master' branch. Thanks again. > > That's generally recommended with new-build at this point, since a lot > of things have improved in cabal 1.25/master since cabal 1.24; > > Also, I'd also recommend consulting > > http://cabal.readthedocs.io/en/latest/nix-local-build-overview.html > > for the latest bleeding edge documentation from `master`; if you notice > something that's unclear in the documentation, it's a documentation bug > and you should either inform us about it, or maybe even provide a > pull-request! Thanks Herbert. -- Ramakrishnan From ram at rkrishnan.org Fri Sep 16 14:02:10 2016 From: ram at rkrishnan.org (Ramakrishnan Muthukrishnan) Date: Fri, 16 Sep 2016 19:32:10 +0530 Subject: building a project with new-* commands In-Reply-To: <87intwaukm.fsf@gmail.com> References: <1474026045.452659.727694897.5FF204AE@webmail.messagingengine.com> <1d65c06c-d999-a915-4ad9-b62e38172135@informatik.uni-kiel.de> <1474029254.468796.727739425.6302C29B@webmail.messagingengine.com> <87intwaukm.fsf@gmail.com> Message-ID: <1474034530.495841.727815721.74166909@webmail.messagingengine.com> On Fri, Sep 16, 2016, at 06:08 PM, Herbert Valerio Riedel wrote: > Hi! > > On 2016-09-16 at 14:34:14 +0200, Ramakrishnan Muthukrishnan wrote: > [..] > > > I will try building and trying the `master' branch. Thanks again. > > That's generally recommended with new-build at this point, since a lot > of things have improved in cabal 1.25/master since cabal 1.24; That did the trick. Thanks. Cheers -- Ramakrishnan From ram at rkrishnan.org Mon Sep 19 07:46:12 2016 From: ram at rkrishnan.org (Ramakrishnan Muthukrishnan) Date: Mon, 19 Sep 2016 13:16:12 +0530 Subject: cabal new-* commands awesomeness Message-ID: <1474271172.1314079.729831345.022B291E@webmail.messagingengine.com> 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 From mikhail.glushenkov at gmail.com Mon Sep 19 11:18:00 2016 From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov) Date: Mon, 19 Sep 2016 12:18:00 +0100 Subject: cabal new-* commands awesomeness In-Reply-To: <1474271172.1314079.729831345.022B291E@webmail.messagingengine.com> References: <1474271172.1314079.729831345.022B291E@webmail.messagingengine.com> Message-ID: Hi, On 19 September 2016 at 08:46, Ramakrishnan Muthukrishnan wrote: > 1. Will the `new' variants become the default? That will be nice! Yes, that's the plan. This won't happen in the next release (2.0), though. > 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? Great, welcome onboard. Take a look at https://github.com/haskell/cabal/labels/meta%3A%20easy. See also https://github.com/haskell/cabal/wiki/Hackathon2015#more-modest-projects. > 3. Is there an irc channel where cabal devs hang out? See https://github.com/haskell/cabal#communicating.