Re: Anybody using the "top-down" solver?

2015-11-08 Thread Oleg Grenrus
I doubt this list has good coverage. You probably should try haskell-cafe? Another way to put this question: Is anybody is still using GHC 6.x? Cheers, Oleg > On 09 Nov 2015, at 06:29, Bardur Arantsson wrote: > > Hi all, > > Just to get input from as many people as

Re: I reorged labels on Cabal's GitHub

2016-07-12 Thread Oleg Grenrus
Great, it looks awesome. Issue template is great idea as well. (for ones who aren’t familiar: https://github.com/blog/2111-issue-and-pull-request-templates ) (I’m +1 for having GitHub stuff under .github/ directory) The issue

Re: Opening up Cabal development

2016-07-14 Thread Oleg Grenrus
> On 14 Jul 2016, at 09:54, Edward Z. Yang wrote: > > Excerpts from Herbert Valerio Riedel's message of 2016-07-13 23:40:06 -0700: >> I.e. write up a specification/proposal outlining motivation (i.e. what >> problem does this solve), specify what the changes are exactly (syntax

Re: I reorged labels on Cabal's GitHub

2016-07-12 Thread Oleg Grenrus
Looks good indeed! I have few questions: - what is purpose of `paging:*` labels, to help people see issues they are interested in? How it’s different from assignees (which can be multiple)? - why “bug” has “ezyang planning to delete this tag”. I’d prefer to have “type: bug” and other “type:*”

Re: I reorged labels on Cabal's GitHub

2016-07-12 Thread Oleg Grenrus
> On 12 Jul 2016, at 18:42, Edward Z. Yang wrote: > > Excerpts from Oleg Grenrus's message of 2016-07-12 04:03:43 -0700: >> Looks good indeed! >> >> I have few questions: >> - what is purpose of `paging:*` labels, to help people see issues they are >> interested in? How it’s

Re: mutex-flags

2017-07-19 Thread Oleg Grenrus
Hi, I proposed multiway flags about a year ago [1]. With that you could write: flag xx values: a, b, c, d if flag(xx == a) build-depends: xx-a if flag(xx == b) build-depends: xx-b if flag(xx == c) build-depends: xx-c if flag(xx == d)

Re: Gearing up for the 2.2 release

2017-12-27 Thread Oleg Grenrus
I had a good success with completing a lot of parser work around Christmas, still on my todo list are: - rewriting InstalledPackageInfo parser using new (parsec) framework, which is (soft) prerequisite to - changing license field to use SPDX expressions SPDX types are already merged, so there

Re: Upgrading Stack to Cabal 2.2

2018-02-20 Thread Oleg Grenrus
Hi Michael, thanks for your comments! - The allBuildInfo change is https://github.com/haskell/cabal/commit/8fc10320a5dc4898927c84ad6a2dce7965ef30db, I agree with Herbert on this. New `allBuildInfo` implementation is correct given the name. There was even a TODO to make that change.

Re: Upgrading Stack to Cabal 2.2

2018-02-20 Thread Oleg Grenrus
t; 2. If we're going to have to treat this as arbitrary text anyway, is > there any reason not to represent it as `newtype TextualLicense = > TextualLicense Text` or similar, and convert immediately with `display`? > > On Tue, Feb 20, 2018 at 6:12 PM, Oleg Grenrus <oleg.gren...@iki.fi >

Re: Upgrading Stack to Cabal 2.2

2018-02-20 Thread Oleg Grenrus
with > >     display . either licenseFromSPDX id > > Is it intentional that there is no Text instance for SPDX.License? > > On Tue, Feb 20, 2018 at 8:02 PM, Oleg Grenrus <oleg.gren...@iki.fi > <mailto:oleg.gren...@iki.fi>> wrote: > > 1. The InstalledPackageInfo