I'm experimenting with converting a large source tree into a Go module. This went pretty smoothly. However, I'm wondering why 'go mod tidy' and 'go mod why' print warnings about symlinks.
These look like: $ go mod tidy warning: ignoring symlink /path/to/some/symlink/dir ... Where a warning line is printed for every symlinked directory in the repo. These warnings make these 'go mod' commands unpleasant to use (you have to scroll through all the junk to see the relevant bits, if any, at the bottom). None of the Go code is in symlinked directories; these all exist for certain projects in other languages. For example, one use of symlinks is as a cheap way to use certain shared JS/CSS assets in multiple sub-projects. Am I holding this wrong, somehow? Can we remove the prints from the Go tool? Or maybe it could only print the warning if there are .go files somewhere in the symlinked dir? If someone can confirm that I'm using the tools as intended, I'll file a bug for further discussion. Thanks! Caleb -- 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/CAGeFq%2BkwZBxB_05%2B2Ca%3DHK7TMXVHN%3DG4X7UKbTcUHNpUPqT_Pg%40mail.gmail.com.
