<p dir="auto">Many packages use <code class="notranslate">Pkg.dir()</code> to find load static resources that aren't Julia code. However, <code class="notranslate">Pkg.dir()</code> always points to <code class="notranslate">~/.julia/v0.x</code>, so this breaks for packages which are stored in <code class="notranslate">julia/usr/share/julia/site/v0.x</code>, for example. It looks like we need a better way to handle this if there isn't one already.</p>
<p dir="auto">Are packages that use <code class="notranslate">Pkg.dir()</code> for this purpose in the wrong, or should <code class="notranslate">Pkg.dir()</code> be smarter? Or should we just only support a single package directory?</p>
<p dir="auto">it works fine if the package is in .julia/v0.x, but if it is somewhere else then it claims there is no <code class="notranslate">test/runtests.jl</code> even if my <code class="notranslate">LOAD_PATH</code> is set such that i can <code class="notranslate">using</code> it.  i know that the recommended dev cycle is to keep packages in .julia, but would it make sense to make Pkg.test() work otherwise?</p>