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.