Firstly thanks for this tool. I have only just installed but it saves me quite a few hours on my .CMD file to manage different ruby-s Good one.
I see that I need to install 7zip to work with the packages command. I already have 7zip on my PC. I wonder if in the future we can use ADD with Package to point to currently installed software. So in my case, I might:
pik package add b:\util\7zip\bin
There could be any number of reasons for this, for example a little while back I found a problem with a 7-zip command line version so I had to stay with the 32bit version for a bit. Most of all I don't like the idea of multiple versions or tools in different silos. If there's a problem (and this has happened ...) you can find you wasted a week looking the package you 'thought' was giving trouble -- Only to discover there's a different version elsewhere giving trouble.
I guess a radical approach is to have like a shared package-gem's repository -- Sorry just dreaming now.
Hi there
Firstly thanks for this tool. I have only just installed but it saves me quite a few hours on my .CMD file to manage different ruby-s Good one.
I see that I need to install 7zip to work with the packages command. I already have 7zip on my PC. I wonder if in the future we can use ADD with Package to point to currently installed software. So in my case, I might:
There could be any number of reasons for this, for example a little while back I found a problem with a 7-zip command line version so I had to stay with the 32bit version for a bit. Most of all I don't like the idea of multiple versions or tools in different silos. If there's a problem (and this has happened ...) you can find you wasted a week looking the package you 'thought' was giving trouble -- Only to discover there's a different version elsewhere giving trouble.
I guess a radical approach is to have like a shared package-gem's repository -- Sorry just dreaming now.
Please consider,
Will