Cabal/cabal-install project ideas for Summer of Code 2018

2017-12-27 Thread Mikhail Glushenkov
Hi *, As you are probably aware, it is again the time of the year to come up with project proposals for the next year's Summer of Code [1]. I've started a Wiki page for collecting Cabal/cabal-install HSoC 2018 project ideas [2] - please feel free to add new entries, edit existing ones and add/remo

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&printer using new (parsec) framework, which is (soft) prerequisite to - changing license field to use SPDX expressions SPDX types are already merged, so

Re: Gearing up for the 2.2 release

2017-12-27 Thread Mikhail Glushenkov
Hi Oleg, On 27 December 2017 at 17:17, Oleg Grenrus wrote: > I had a good success with completing a lot of parser work around Christmas, > still on my todo list are: > > - rewriting InstalledPackageInfo parser&printer using new (parsec) > framework, which is (soft) prerequisite to > - changing li

Re: Gearing up for the 2.2 release

2017-12-27 Thread Daniel Trstenjak
Most likely the stability of the pretty printing of a GenericPackageDescription isn't considered that important. I just wanted to mention that the order of fields in the stanzas changed from 'Cabal 1.24/2.0' to the current HEAD. Greetings, Daniel name: setup-config version: 0.1 cabal-version: >=1

Re: Gearing up for the 2.2 release

2017-12-27 Thread Mikhail Glushenkov
Hi Daniel, On 27 December 2017 at 17:43, Daniel Trstenjak wrote: > Most likely the stability of the pretty printing of a > GenericPackageDescription > isn't considered that important. > > I just wanted to mention that the order of fields in the stanzas changed > from 'Cabal 1.24/2.0' to the curr