Cameron Eagans
Cameron Eagans
@christopher-hopper Please open an issue for that. I'm not opposed to adding additional optional metadata fields for `Patch` objects in the 2.x releases.
I've made a note to handle this in `main`.
I haven't added it yet. Feel free!
No, sorry. 1.x isn't really changing at this point. 2.x will likely solve your problem, as a given patch should only ever be downloaded once (provided you keep the cache...
No argument here. Want to take a crack at writing that @AlexSkrypnyk ?
What version of git do you have installed in your chroot?
No response.
Step 3: the intent is that you currently have a patched dependency (say `symfony/process`). If you remove the patch that is defined for `symfony/process`, you need to go `rm -r...
It was extraordinarily complex in 1.x. Probably one of the biggest sources of bugs. There are lots of edge cases wrt installing/updating a single package (vs your entire project). It...
I uninstalled vagrant and then did this: ``` wget https://raw.githubusercontent.com/Homebrew/homebrew-cask/3fcf62641e6594340a09fda1cf1bfb3be505cf0c/Casks/v/vagrant.rb brew install --cask vagrant.rb vagrant plugin install vagrant-google ``` That installed the right version of vagrant and the plugin version...