IMHO Don't do it for a library. Let your users decide if they prefer to commit their vendor directory or not.
Do whatever you want for a standalone project. JFB Le samedi 28 juillet 2018 20:43:04 UTC+2, nafis a écrit : > > Suppose I'm making a library and it does reference some other library not > part of the standard library. I want to vendor those so that my library > doesn't fail if the other 3rd party developer deletes their library or > major changes of their library(I know this sound like stupid design). And I > want to push the vendor folder on my library repo. My question: Is this > the bad idea keep a vendor folder on the library repo. > > Thank you for your time. > -- 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.
