New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The --nimblePath is additive; need a pain-free workaround #12601
Comments
I've been recently having issues with this too..
My use case is there I want nim to look at only a sandboxed/stable nimble pkg collection in one directory and exclude my personal We essentially need a PS: Setting the env var |
The Right now, we are only covering Nimble changes to support this mode but step two is to address how this will be communicated to Nim. There may be code changes required in Nim as well but the current idea is to use nim.cfg to communicate This also ties into this issue where Nimble nuances needn't be known to Nim and ideally the |
I'm really curious about the use cases for this feature...
You can already get pretty far in assuring this by just using |
I'm building lockfiles. |
(cherry picked from commit 738c957)
Per title,
--nimblePath
is an all-or-nothing feature that precludes the specification of an authoritative alternative source of imports.Edit. title was misleading
The text was updated successfully, but these errors were encountered: