From gershomb at gmail.com  Mon Dec  4 02:08:56 2017
From: gershomb at gmail.com (Gershom B)
Date: Sun, 3 Dec 2017 21:08:56 -0500
Subject: new cabal install binaries
Message-ID: <CAM8RHpF1p2zQfAWwDn96TLFQ38EyCWDegQWfiMODAhzd_m=2xA@mail.gmail.com>

when we build the new platform we're going to have new cabal-install
binaries for 2.0.1.0. It would be better if we provided the same ones
as provided on the cabal website. Is there anyone lined up to build
any of these, or would you like the platform team to provide you with
the binaries we build as well? (i know i've done mac in the past, and
will happily do so again, but typically there have been other sources
for linux and windows binaries).

Cheers,
Gershom

From mikhail.glushenkov at gmail.com  Mon Dec  4 10:09:13 2017
From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov)
Date: Mon, 4 Dec 2017 10:09:13 +0000
Subject: new cabal install binaries
In-Reply-To: <CAM8RHpF1p2zQfAWwDn96TLFQ38EyCWDegQWfiMODAhzd_m=2xA@mail.gmail.com>
References: <CAM8RHpF1p2zQfAWwDn96TLFQ38EyCWDegQWfiMODAhzd_m=2xA@mail.gmail.com>
Message-ID: <CA+tcxkB9br094Veozn4oyHQw2=z4Gje-YudiDar_Thf8r1W3MQ@mail.gmail.com>

Hi Gershom,

On 4 December 2017 at 02:08, Gershom B <gershomb at gmail.com> wrote:
> when we build the new platform we're going to have new cabal-install
> binaries for 2.0.1.0. It would be better if we provided the same ones
> as provided on the cabal website. Is there anyone lined up to build
> any of these, or would you like the platform team to provide you with
> the binaries we build as well?

Usually it's me who builds the Linux and Windows binaries. I'll do
that today or tomorrow. Note that I'll be using the just released
Cabal-2.0.1.1 instead of Cabal-2.0.1.0 that comes with GHC 8.2.2.

> (i know i've done mac in the past, and
> will happily do so again, but typically there have been other sources
> for linux and windows binaries).

If you could send me a Mac binary of cabal-install-2.0.0.1 compiled
against Cabal-2.0.1.1, that'd be appreciated. Or you can just upload a
compressed tar.xz to
https://www.haskell.org/cabal/release/cabal-install-2.0.0.1/.

From mikhail.glushenkov at gmail.com  Fri Dec  8 07:29:03 2017
From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov)
Date: Fri, 8 Dec 2017 07:29:03 +0000
Subject: new cabal install binaries
In-Reply-To: <CAM8RHpF1p2zQfAWwDn96TLFQ38EyCWDegQWfiMODAhzd_m=2xA@mail.gmail.com>
References: <CAM8RHpF1p2zQfAWwDn96TLFQ38EyCWDegQWfiMODAhzd_m=2xA@mail.gmail.com>
Message-ID: <CA+tcxkD6+8G_A6id1XM7y2EfyjygwwgypTXV3sb6mh6Qu=eK1Q@mail.gmail.com>

Hi Gershom,

On 4 December 2017 at 02:08, Gershom B <gershomb at gmail.com> wrote:
> when we build the new platform we're going to have new cabal-install
> binaries for 2.0.1.0. It would be better if we provided the same ones
> as provided on the cabal website. Is there anyone lined up to build
> any of these, or would you like the platform team to provide you with
> the binaries we build as well?

Binaries for the 2.0.0.1 release are up now on haskell.org/cabal.

From mikhail.glushenkov at gmail.com  Fri Dec  8 08:01:49 2017
From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov)
Date: Fri, 8 Dec 2017 08:01:49 +0000
Subject: [ANN] Cabal 2.0.1.1/cabal-install 2.0.0.1 released
Message-ID: <CA+tcxkA=8tj14yeyGPUPBjBL34-n9KptoA--nMW0Bv4ES1n-DA@mail.gmail.com>

Hi *,

Cabal 2.0.1.1 and cabal-install 2.0.0.1 are now available from
Hackage and the download page:

http://hackage.haskell.org/package/Cabal-2.0.1.1
http://hackage.haskell.org/package/cabal-install-2.0.0.1
https://www.haskell.org/cabal/download.html

Changes in this release:

Cabal 2.0.1.1:

    * Don't pass `other-modules` to stub executable for detailed-0.9
    (#4918).
    * Hpc: Use relative .mix search paths (#4917).

cabal-install 2.0.0.1:

    * Support for GHC's numeric -g debug levels (#4673).
    * Demoted 'scope' field version check to a warning (#4714).
    * Fixed verbosity flags getting removed before being passed to
    'printPlan' (#4724).
    * Added a '--store-dir' option that can be used to configure the
    location of the build global build store (#4623).
    * Turned `allow-{newer,older}` in `cabal.project` files into an
    accumulating field to match CLI flag semantics (#4679).
    * Improve success message when `cabal upload`ing documentation
    (#4777).
    * Documentation fixes.


Cheers,
Mikhail

From mikhail.glushenkov at gmail.com  Fri Dec 15 16:40:11 2017
From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov)
Date: Fri, 15 Dec 2017 16:40:11 +0000
Subject: Gearing up for the 2.2 release
Message-ID: <CA+tcxkC6ahPytDccxYptKFHYFMqQ47c+=OkvLFXNC-t5M7yJjg@mail.gmail.com>

Hi *,

It is time to start planning for the 2.2 release of
Cabal/cabal-install. The original plan was to do it before the end of
the year, however, given the current state of HEAD and the fact that
GHC 8.4 is going to be released in February, I think it won't be a
tragedy if we delay 2.2 a little. My current plan is to cut the 2.2
branch around January 15th, and make the release 2-3 weeks after that.
So please hurry if there's something you absolutely want to get into
2.2.

Current release blockers/stuff that I really want to see included:

* Herbert's work on the forwards-compat scheme
(https://github.com/haskell/cabal/issues/4899)
* Duncan's target package names stuff
(https://github.com/haskell/cabal/pull/4889)
* Oleg's remaining parser PRs and SPDX work.
* Some other currently unmerged PRs that are not marked blocked or are
easy to get into mergeable shape.


Cheers,
Mikhail

From mikhail.glushenkov at gmail.com  Wed Dec 27 14:36:55 2017
From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov)
Date: Wed, 27 Dec 2017 15:36:55 +0100
Subject: Cabal/cabal-install project ideas for Summer of Code 2018
Message-ID: <CA+tcxkAXrt6JqOBYPkEzKVe2v6fQxD-JU3dDqX0yAEjs4EDqfg@mail.gmail.com>

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/remove yourself to/from the list of potential mentors.
Once the list of potential projects is more or less complete, I'll
send a PR to the Summer of Haskell GitHub repo.

Herbert tells me that the list of proposals should be finished before
January 4th, so please hurry!


Cheers,
Mikhail


[1] https://mail.haskell.org/pipermail/haskell-cafe/2017-December/128365.html
[2] https://github.com/haskell/cabal/wiki/%5BG,H%5DSoC-2018-Project-Ideas

From oleg.grenrus at iki.fi  Wed Dec 27 16:17:13 2017
From: oleg.grenrus at iki.fi (Oleg Grenrus)
Date: Wed, 27 Dec 2017 18:17:13 +0200
Subject: Gearing up for the 2.2 release
In-Reply-To: <CA+tcxkC6ahPytDccxYptKFHYFMqQ47c+=OkvLFXNC-t5M7yJjg@mail.gmail.com>
References: <CA+tcxkC6ahPytDccxYptKFHYFMqQ47c+=OkvLFXNC-t5M7yJjg@mail.gmail.com>
Message-ID: <2D420BAF-DC33-4AAC-8F7C-E5D64B64DA94@iki.fi>

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 there aren't much left, expect 2-3 PRs early next year. 

I'm heading off to no-keyboard place.

- Oleg

Sent from my iPhone

> On 15 Dec 2017, at 18.40, Mikhail Glushenkov <mikhail.glushenkov at gmail.com> wrote:
> 
> Hi *,
> 
> It is time to start planning for the 2.2 release of
> Cabal/cabal-install. The original plan was to do it before the end of
> the year, however, given the current state of HEAD and the fact that
> GHC 8.4 is going to be released in February, I think it won't be a
> tragedy if we delay 2.2 a little. My current plan is to cut the 2.2
> branch around January 15th, and make the release 2-3 weeks after that.
> So please hurry if there's something you absolutely want to get into
> 2.2.
> 
> Current release blockers/stuff that I really want to see included:
> 
> * Herbert's work on the forwards-compat scheme
> (https://github.com/haskell/cabal/issues/4899)
> * Duncan's target package names stuff
> (https://github.com/haskell/cabal/pull/4889)
> * Oleg's remaining parser PRs and SPDX work.
> * Some other currently unmerged PRs that are not marked blocked or are
> easy to get into mergeable shape.
> 
> 
> Cheers,
> Mikhail
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/cabal-devel/attachments/20171227/ad1d6761/attachment.html>

From mikhail.glushenkov at gmail.com  Wed Dec 27 16:21:31 2017
From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov)
Date: Wed, 27 Dec 2017 17:21:31 +0100
Subject: Gearing up for the 2.2 release
In-Reply-To: <2D420BAF-DC33-4AAC-8F7C-E5D64B64DA94@iki.fi>
References: <CA+tcxkC6ahPytDccxYptKFHYFMqQ47c+=OkvLFXNC-t5M7yJjg@mail.gmail.com>
 <2D420BAF-DC33-4AAC-8F7C-E5D64B64DA94@iki.fi>
Message-ID: <CA+tcxkBvxw2PWhLiKctJYq37chshRkVo_+iw-Q1nwm4xvCsZ1A@mail.gmail.com>

Hi Oleg,

On 27 December 2017 at 17:17, Oleg Grenrus <oleg.grenrus at iki.fi> 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 license field to use SPDX expressions
>
> SPDX types are already merged, so there aren't much left, expect 2-3 PRs
> early next year.
>
> I'm heading off to no-keyboard place.

Great! Have fun!


Cheers,

From daniel.trstenjak at gmail.com  Wed Dec 27 16:43:08 2017
From: daniel.trstenjak at gmail.com (Daniel Trstenjak)
Date: Wed, 27 Dec 2017 17:43:08 +0100
Subject: Gearing up for the 2.2 release
In-Reply-To: <CA+tcxkBvxw2PWhLiKctJYq37chshRkVo_+iw-Q1nwm4xvCsZ1A@mail.gmail.com>
References: <CA+tcxkC6ahPytDccxYptKFHYFMqQ47c+=OkvLFXNC-t5M7yJjg@mail.gmail.com>
 <2D420BAF-DC33-4AAC-8F7C-E5D64B64DA94@iki.fi>
 <CA+tcxkBvxw2PWhLiKctJYq37chshRkVo_+iw-Q1nwm4xvCsZ1A@mail.gmail.com>
Message-ID: <20171227164308.GA19358@octa>

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
-------------- next part --------------
name: setup-config
version: 0.1
cabal-version: >=1.9.2
build-type: Simple
license: UnspecifiedLicense
maintainer: daniel.trstenjak at gmail.com
author: Daniel Trstenjak

library
    exposed-modules:
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.7 && <0.9
    hs-source-dirs: src
    other-modules:
        Paths_setup_config

executable cabal-bounds
    main-is: ExeMain1.hs
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <0.9
    cpp-options: -DCABAL
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W

executable other-exe
    main-is: ExeMain2.hs
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <0.9
    cpp-options: -DCABAL
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W

test-suite some-test
    type: exitcode-stdio-1.0
    main-is: TestMain1.hs
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <0.9
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W
test-suite other-test
    type: exitcode-stdio-1.0
    main-is: TestMain2.hs
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <1.0
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W
-------------- next part --------------
name: setup-config
version: 0.1
license: UnspecifiedLicense
maintainer: daniel.trstenjak at gmail.com
author: Daniel Trstenjak
cabal-version: >=1.9.2
build-type: Simple

library
    exposed-modules:
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.7 && <0.9

executable cabal-bounds
    main-is: ExeMain1.hs
    scope: unknown
    cpp-options: -DCABAL
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <0.9

executable other-exe
    main-is: ExeMain2.hs
    scope: unknown
    cpp-options: -DCABAL
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <0.9

test-suite some-test
    type: exitcode-stdio-1.0
    main-is: TestMain1.hs
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <0.9

test-suite other-test
    type: exitcode-stdio-1.0
    main-is: TestMain2.hs
    hs-source-dirs: src
    other-modules:
        Paths_setup_config
        CabalBounds.Args
        CabalBounds.Command
        CabalBounds.Execute
        CabalBounds.Lenses
    ghc-options: -W
    build-depends:
        base >=3,
        A >=0.1 && <0.2,
        B >=0.2 && <0.4,
        C >=0.2.5 && <0.4,
        D >=0.8.2 && <1.0

From mikhail.glushenkov at gmail.com  Wed Dec 27 16:49:07 2017
From: mikhail.glushenkov at gmail.com (Mikhail Glushenkov)
Date: Wed, 27 Dec 2017 17:49:07 +0100
Subject: Gearing up for the 2.2 release
In-Reply-To: <20171227164308.GA19358@octa>
References: <CA+tcxkC6ahPytDccxYptKFHYFMqQ47c+=OkvLFXNC-t5M7yJjg@mail.gmail.com>
 <2D420BAF-DC33-4AAC-8F7C-E5D64B64DA94@iki.fi>
 <CA+tcxkBvxw2PWhLiKctJYq37chshRkVo_+iw-Q1nwm4xvCsZ1A@mail.gmail.com>
 <20171227164308.GA19358@octa>
Message-ID: <CA+tcxkBXzKDE-fVizp3dOb_zXkPd2hzs4YCSkCzt-ek1wtuQwA@mail.gmail.com>

Hi Daniel,

On 27 December 2017 at 17:43, Daniel Trstenjak
<daniel.trstenjak at gmail.com> 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 current HEAD.

Yep, I don't think we should spend time on fixing that (especially
given how 'cabal format' is not considered stable). But thanks for
letting us know, I think I'll mention that in the change log.