You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used to let el-get handle all ELisp add-on packages in my system. However, since Debian has now hundreds of elpa-* packages, I would prefer those of Debian instead of having el-get automatically installing them for me. In order to make things clearer, imagine that I installed dash through apt in my Debian system (with, say, apt install elpa-dash). Now, if I require, for instance, org-ref through el-get (with, say, (el-get-bundle og-ref)). Since dash is a dependency of org-ref, then el-get will download and install dash, even though it is already system-wide installed (in /usr/share/emacs/site-lisp/elpa/dash-2.17.0). Is there a way to prevent this?
The text was updated successfully, but these errors were encountered:
I used to let el-get handle all ELisp add-on packages in my system. However, since Debian has now hundreds of elpa-* packages, I would prefer those of Debian instead of having el-get automatically installing them for me. In order to make things clearer, imagine that I installed dash through apt in my Debian system (with, say,
apt install elpa-dash
). Now, if I require, for instance, org-ref through el-get (with, say,(el-get-bundle og-ref)
). Since dash is a dependency of org-ref, then el-get will download and install dash, even though it is already system-wide installed (in/usr/share/emacs/site-lisp/elpa/dash-2.17.0
). Is there a way to prevent this?The text was updated successfully, but these errors were encountered: