3 ms·
2 problems: - libraries are duplicated left and right. If I want to use the same library in multiple projects, it will be in each project's lib (note that this
by rakoo 12y ago
2 problems:
- libraries are duplicated left and right. If I want to use the same library in multiple projects, it will be in each project's lib (note that this is how you'd vendor, but it's something else)
- resetting env for each command you run sounds heavier, and the day will come when you will forget to do it and you'll run into problems.
- falcolas 12y agoDuplication depends on how you pull them in. For 3rd party libs, you'll pull them in via 'go get', and they will reside in the normal GOROOT, which is appropriate. It's just the libs you write for the particular project which would go down the local lib directory. Resetting the env isn't my preferred choice, but if you put it in a make file, it becomes hard to forget. Especially if you are in the habit of reusing make files between projects with a few customizations, which is my preferred setup.