You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With vgo get -u and vgo get -p you'll be able to update dependencies which includes a focus on the patch file level. Instead of doing everything or individual dependencies at the console it would be useful to have a file that holds the rules per dependency. For example, there are 3 dependencies A, B, and C. For A and C the equivalent of -u is used while on dependency B -p is used. vgo along with a config file will update following the rules.
The text was updated successfully, but these errors were encountered:
You're asking for a configuration file to change the meaning of vgo get -u and vgo get -p on a per-module basis. I don't see this happening. The go command eschews this kind of customization complexity. If you want to make it easier to update certain dependencies a certain way, I would suggest instead a shell script. In your example:
vgo get -u A C
vgo get -p B
(If you name it update.bat and mark it executable it will work equally well on Unix and Windows. :-) )
Note that the get commands don't work the right way today to accept those arguments, but the plan is to make them work. Perhaps the lack of being able to write those commands today is what motivated the suggestion of a separate config file.
With
vgo get -u
andvgo get -p
you'll be able to update dependencies which includes a focus on the patch file level. Instead of doing everything or individual dependencies at the console it would be useful to have a file that holds the rules per dependency. For example, there are 3 dependencies A, B, and C. For A and C the equivalent of-u
is used while on dependency B-p
is used.vgo
along with a config file will update following the rules.The text was updated successfully, but these errors were encountered: