You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
This is wrong. Markdown exists on PATH and was never installed to this location. ./configure made this up because it couldn't find markdown.
The root cause is shocco's ./configure script, which is why I'm filing this here vs. against the brew formula. It explicitly overrides the user's PATH and reconstructs it from scratch, guessing at likely install locations of dependent tools such as pygments and markdown, including the default homebrew install prefix. It's not clear why the script reconstructs PATH, but this seems like a brittle policy for the reason illustrated in this issue.
Proposed fix
If brew is available, use brew --prefix to figure this out.
The text was updated successfully, but these errors were encountered:
@adamv Yes, I'd prefer leaving PATH alone and using which as well. I was mostly going with the (unspoken) assumption that there was some reason to reconstruct PATH in the first place that I wasn't aware of.
Repro steps
/usr/local
. E.g./opt/brew
brew install --HEAD shocco
which shocco
Actual result
NOTE: markdown was correctly installed as a dependency by the brew formula and exists on PATH.
Expected result
Works
The first-order failure cause is due to this line in the built shocco script:
This is wrong. Markdown exists on PATH and was never installed to this location.
./configure
made this up because it couldn't find markdown.The root cause is shocco's
./configure
script, which is why I'm filing this here vs. against the brew formula. It explicitly overrides the user's PATH and reconstructs it from scratch, guessing at likely install locations of dependent tools such as pygments and markdown, including the default homebrew install prefix. It's not clear why the script reconstructs PATH, but this seems like a brittle policy for the reason illustrated in this issue.Proposed fix
If brew is available, use
brew --prefix
to figure this out.The text was updated successfully, but these errors were encountered: