PR action-required tag, and a Phabricator instance

2015-09-24 Thread Edward Z. Yang
Hey all, Two quick reports for Cabal: 1. I've tagged all PRs as either cabal-install/library. This should help triage, since the nature of patches to these different projects can be quite different. 2. I've tagged PRs that are KNOWN to not be mergeable (either due to Travis failure or something

Re: Global Constraints for Cabal and also Release Plan?

2015-09-24 Thread Bardur Arantsson
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

Re: Global Constraints for Cabal and also Release Plan?

2015-09-24 Thread Gershom B
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

Re: Global Constraints for Cabal and also Release Plan?

2015-09-24 Thread Mikhail Glushenkov
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

Re: Global Constraints for Cabal and also Release Plan?

2015-09-24 Thread Gershom B
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

Re: Global Constraints for Cabal and also Release Plan?

2015-09-24 Thread Mikhail Glushenkov
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

Re: Global Constraints for Cabal and also Release Plan?

2015-09-24 Thread Bardur Arantsson
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