On 17-03-09 00:13:59, Iru Cai via arch-general wrote:
Go programs are compiled to a single binary that do not link to other go libraries, so they doesn't depend on other go packages.
You answered your question here, haven't you?
I'm also confused when I see node.js packages. I see many of the packages are built using just an `npm install' so the packaging process will pull a lot of code, but I think it's better than that in go because the node.js packages are installed in the user home so that it won't be installed again when another node.js package needs the same dependency.
Are you saying that building a go program should re-use user-installed go packages? Does https://wiki.archlinux.org/index.php/Go_package_guidelines answer your question? -- Pierre Neidhardt