<p>I have removed all source directories in src on the suggestion of a developer to fix a git error, however it doesn't seem like <code>go get</code> keeps a list of the links of all installed packages so <code>go get -u all</code> doesn't work anymore. Is there any way to redownload the sources of all installed packages?</p>
<hr/>**评论：**<br/><br/>kisielk: <pre><p>In <code>$GOPATH/pkg/</code> there's a tree of subdirectories of previously compiled packages. You can write a script or program to walk this tree and reassemble all the original import paths.</p></pre>pappogeomys: <pre><p>You've removed the closest thing there is to a list of the installed packages. Just <code>go get</code> new packages as needed. </p></pre>greenreflection: <pre><p>This was my fear. It's a bit disappointing.</p></pre>pappogeomys: <pre><p>What exactly are you concerned with? I've started with an empty GOPATH countless times. If you never notice that you're missing a package you once had, are you really missing it? </p></pre>greenreflection: <pre><p>Well, the only issue is <code>go get -u all</code> not working and getting stuck with old packages.</p></pre>pappogeomys: <pre><p>You're not stuck with old packages, because you don't have them any more. Even the very rare binary-only packages require a source file. Anything you build will require fetching the source, which will get you the same thing as <code>go get -u</code>. </p>
<p>Dependencies should be managed carefully, not just with blanket updates. In almost 5 years of writing Go professionally, I've never once used <code>go get -u all</code>. </p></pre>BaconBytes42: <pre><p>yeah use dep</p></pre>greenreflection: <pre><p>Isn't dep for managing dependencies of a single package and not managing all packages in $GOPATH/src?</p></pre>BaconBytes42: <pre><p>True. Have to have a reference to what you want/need. If there are no files there, nothing is going to know what you had.</p>
<p>Maybe write up a script to dep each project you have and install globally?</p></pre>
