I have a bunch of software git-cloned into my
site-lisp/ directory. It and all of its sub-directories are in my
load-path. The problem I noticed is that
package-install sometimes insists on pulling dependencies into
elpa/ even when such packages already exist in
site-lisp/. To be more specific:
package-install helm-descbinds insists on installing Helm 1.5 even though not only do I have the latest helm in in my
site-lisp/helm/ but by the time the install gets called,
(require 'helm-config) will have happened.
Who's at fault here? Is it the
helm-descbinds package itself and I should be raising an issue with its maintainers? Or is there some obvious knob I need to turn in packages so the existing functionality gets picked up? Basically I just want to be sure that stuff in
site-lisp/ gets precedence. This very well maybe the case already, but then why install stuff that's already available?