Skip to main content
Emacs

Return to Question

deleted 16 characters in body; edited tags; edited title
Source Link
Gilles 'SO- stop being evil'
Gilles 'SO- stop being evil'
  • 23.3k
  • 4
  • 60
  • 94

package-install doesn't pick up package-dependenciesdependencies that are already installedin site-lisp

I have a bunch of software git-cloned into my site-lisp/site-lisp/ directory. It and all of its sub-directories are in my load-pathload-path. The problem I noticed is that package-installingpackage-install sometimes insists on pulling dependencies into elpa/elpa/ even when such packages already exist in site-lisp/site-lisp/. To be more specific:

package-install helm-descbinds insists on installing helmHelm 1.5 even though not only do I have the latest helm in in my load-pathload-path from site-lisp/helm/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-descbindshelm-descbinds package itself and I should be raising an issue with its maintainers or there's? 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/site-lisp/ gets precedence. This very well maybe the case already, but then why install stuff that's already available. Thanks.?

package-install doesn't pick up package-dependencies already installed

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-installing 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 load-path from site-lisp/helm/ but by the time the install gets called (require 'helm-config) will have happened.

Who's at fault here the helm-descbinds package itself and I should be raising an issue with its maintainers or there's 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. Thanks.

package-install doesn't pick up dependencies that are already in site-lisp

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 load-path from 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?

Source Link
zeRusski
zeRusski
  • 335
  • 1
  • 8

package-install doesn't pick up package-dependencies already installed

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-installing 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 load-path from site-lisp/helm/ but by the time the install gets called (require 'helm-config) will have happened.

Who's at fault here the helm-descbinds package itself and I should be raising an issue with its maintainers or there's 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. Thanks.