Hey, Then why is it called mvs? I don't understand what package system would give me 1.3.49, if I require 1.2.0 and my dependency requires 1.1.0.
I'll read a bit more about it, but you may have decreased my level of go module hate by a bit, sir :) Thanks, -- Antoine Mercadal > On Sep 13, 2019, at 11:05 PM, Jakob Borg <ja...@kastelo.net> wrote: > >> On 14 Sep 2019, at 01:52, anto...@aporeto.com wrote: >> >> but require 1.2.0 will not work if another dependency requires the same >> package at version 1.1.0 thanks to mvs. >> >> So either I'm wrong and I did not understand mvs, in that case I would like >> to get enlighten, or I got that right and that comforts me in my deep hate >> of mvs. > > Luckily, you're wrong on this point. MVS means that if you require 1.2.0 and > some dependency requires 1.1.0, you'll both get 1.2.0. (And not, say, 1.3.49). > > //jb -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/BF3BD86E-47E7-4D85-A25E-EFA2E42C020E%40aporeto.com.
