-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support for pinning Lua by default #1934
Conversation
Thanks for the PR. Trying to determine the default Lua version by using a subprocess seems slow and brittle, and is probably not something we want to be doing in conda. In particular because only very few people use Lua, but all conda users are going to be affected by this change. As far as I'm concerned, conda (unlike conda-build) should not have any features hard-coded to support special languages. My point of view is that conda is a language (which includes Python) agnostic package manager. Conda-build, on the other hand, may (and does) contain special code to support all sorts of commonly used scenarios. |
Thanks for the comment. Should I hard-code the Lua version? Use of Lua in
|
Turns out everything but the default version of Python is unused in the "pinning" section of |
It seems a bit strange to me that it should be necessary to set a default version to |
I can set it to whatever's most innocuous, but I need something to not On Sun, Jan 3, 2016 at 10:48 AM, Ilan Schnell notifications@github.com
|
If you add a small comment why |
Done |
Support for pinning Lua by default
Hi there, thank you for your contribution to Conda! This pull request has been automatically locked since it has not had recent activity after it was closed. Please open a new issue or pull request if needed. |
This pull request is a small accompaniment for a larger PR in the
conda-build
repo here: conda/conda-build#719This pull request pins Lua versions by default, because Lua releases, like Python, do not occur often, but when they do, they often break packages.