commercialhaskell/stack

Set $ACLOCAL_PATH in `stack exec` appropriately

Open

#3,501 创建于 2017年10月20日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)Haskell (4,060 star) (848 fork)batch import
component: Windowshelp wantedtype: bug

描述

As I found out in this Phabricator thread, stack exec [--no-ghc-package-path] bash doesn't set $ACLOCAL_PATH. I'm not sure why this is. When starting a regular mingw64 session or Git Bash (even stack exec mintty and choosing mingw64), the paths are set correctly.

Steps to reproduce

  1. stack exec bash on a Windows machine (AFAICT any stack config will do)
  2. Realise that ehco $ACLOCAL_PATH is empty
$ stack --version
Version 1.5.1, Git revision 600c1f01435a10d127938709556c1682ecfd694e x86_64 hpack-0.17.1

贡献者指南

技术栈
无
领域
clitooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic understanding of stackKnowledge of environment variables
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
70
研究方向
Investigate how `stack exec` sets environment variables by examining the `Stack.Exec` module source code. Look at the Phabricator thread (https://phabricator.haskell.org/D3918) for background on why ACLOCAL PATH is not propagated. Determine the appropriate location to set ACLOCAL PATH and consider platform specific behavior, especially on Windows with MSYS2. Check existing tests for environment variable propagation to ensure no regressions.