Hi Gershom,
On 22 September 2015 at 00:11, Gershom B wrote:
> Any more feedback on this? And also, do we have any plans for an
> upcoming Cabal release?
Re: next release, I think we should do one in the near future, but I'd
like to see some outstanding PRs merged first. I have the following
prel
On September 25, 2015 at 5:43:38 PM, Gershom B (gersh...@gmail.com) wrote:
> Ah this looks like it only takes hold for the simple build-type and not
> “build-type: configure”
> for use with autoconf. (i.e. the “building network” case). I don’t quite see
> what’s going
> on in terms of how an
On September 24, 2015 at 12:16:29 PM, Mikhail Glushenkov
(the.dead.shall.r...@gmail.com) wrote:
> On 24 September 2015 at 17:56, Gershom B wrote:
> > Consider for example if we have a configure build-type, that runs an
> > autoconf script.
> It is not enough that the executable we run be in the
On 09/24/2015 05:06 PM, Gershom B wrote:
> On September 24, 2015 at 11:01:53 AM, Bardur Arantsson (s...@scientician.net)
> wrote:
>> On 09/22/2015 12:11 AM, Gershom B wrote:
>> [--snip--]
>>>
>>> The proposal there would be to add an env variable (perhaps
>>> CABAL_PATH_PREFIX) which, if it existe
On 24 September 2015 at 17:56, Gershom B wrote:
> Consider for example if we have a configure build-type, that runs an autoconf
> script. It is not enough that the executable we run be in the path, but also
> that the “path” available to the autoconf script be amended as well.
Yes, 'extra-prog-
On September 24, 2015 at 11:52:51 AM, Mikhail Glushenkov
(the.dead.shall.r...@gmail.com) wrote:
> On 24 September 2015 at 17:06, Gershom B wrote:
> > So, I want MSys2 tools in my path but _only_ when I am building cabal
> > packages, and not
> otherwise.
>
> IIUC, 'extra-prog-path' in '~/.cab
On 24 September 2015 at 17:06, Gershom B wrote:
> So, I want MSys2 tools in my path but _only_ when I am building cabal
> packages, and not otherwise.
IIUC, 'extra-prog-path' in '~/.cabal/config' already does what you
want. It looks like it also supports multiple directories, using comma
as sepa
On September 24, 2015 at 11:01:53 AM, Bardur Arantsson (s...@scientician.net)
wrote:
> On 09/22/2015 12:11 AM, Gershom B wrote:
> [--snip--]
> >
> > The proposal there would be to add an env variable (perhaps
> > CABAL_PATH_PREFIX) which, if it existed, would be added to the path
> > before runnin
On 09/22/2015 12:11 AM, Gershom B wrote:
[--snip--]
>
> The proposal there would be to add an env variable (perhaps
> CABAL_PATH_PREFIX) which, if it existed, would be added to the path
> before running child processes (such as those kicked off by
> build-type:configure). That way windows environm
Any more feedback on this? And also, do we have any plans for an
upcoming Cabal release?
Braindump here:
Once this lands and we have a cabal release, we can do a trial run of
a new minimal platform release. So I'm inclined to try to target a
cabal release for sooner than later if possible, to ena
I've changed Freeze.hs to also respect this flag, and submitted a pull request:
https://github.com/haskell/cabal/pull/2820
--Gershom
On Thu, Sep 10, 2015 at 6:45 PM, Gershom B wrote:
> Hi all. I've got a branch of cabal with a new feature:
> https://github.com/gbaz/cabal/tree/constraints-config
Hi all. I've got a branch of cabal with a new feature:
https://github.com/gbaz/cabal/tree/constraints-config
This lets you either pass `constraints-file` on the command line or in
the ~/.cabal/config file.
The constraints-file serves as a "default" cabal.config file for
freezes should one not be
12 matches
Mail list logo
