Instead of thanking all reporters individually I'll do it here. I didn't expect a clear winner but some of the rationales for prefering one dependency mgmt tool over the other became more clear to me.
To sum it up: I'll stick with godeps. It seems it hits somewhere the sweetspot between following go's way to organize source code and provides a thin, meaningful utility layer above. I aknowledge again gb - an inredible effort and again the reasons drawn are understandable. But I am not adventurous enough and rather stick with the crowd. I feared that this delecate topic, comparable to browser wars, will start some heated discussions, that was not my intention. Thanks to the contributors to this discussion! -- 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. For more options, visit https://groups.google.com/d/optout.
