We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I install either mingw32 or mingw64, it overwrites the other one using the same name
ruby-2.0.0-p0
The text was updated successfully, but these errors were encountered:
Hello @zhon, this is a known limitation of current Pik.
I suggest you manually download the x64 package, extract it and use pik add to add the other version.
pik add
For example, I manually install all my rubies, this is how my configuration looks like:
"[ruby-]2.0.0-p0": :alias: "200" :path: !ruby/object:Pathname path: C:/Users/Luis/Tools/Ruby/ruby-2.0.0-p0-i386-mingw32/bin :version: | ruby 1.9.3p392 (2013-02-22) [i386-mingw32] "[ruby-]2.0.0-p0-x64": :alias: 200-64 :path: !ruby/object:Pathname path: C:/Users/Luis/Tools/Ruby/ruby-2.0.0-p0-x64-mingw32/bin :version: | ruby 2.0.0p0 (2013-02-24) [x64-mingw32]
Sorry, something went wrong.
After using pik add, I ended up with the same name. So after 'pik add ' you must change the config file?
Where is the pik config file so I can edit it?
So after 'pik add ' you must change the config file?
Yeah, I ended editing the file manually and adding alias key to allow me easy reference it.
alias
%USERPROFILE%\.pik\config.yml
No branches or pull requests
When I install either mingw32 or mingw64, it overwrites the other one using the same name
ruby-2.0.0-p0
The text was updated successfully, but these errors were encountered: