Permalink
Browse files

package-install: Don't do a complete `package-initialize'.

There isn't a reason why a full initialization needs to be run after installing
each individual package. This also avoids problems with archive setup, since
initialization reads the archive contents, but simple activation does not.

Signed-off-by: Dan Hackney <dan@haxney.org>
  • Loading branch information...
1 parent ecee915 commit b69b25e676bcb8a559ee86985151e3856e8ac78e @haxney committed Jun 20, 2010
Showing with 11 additions and 2 deletions.
  1. +10 −0 package-test.el
  2. +1 −2 package.el
View
@@ -738,6 +738,16 @@
(package-install (make-package :name 'not-found))
'completed)
(error err)))
+ (expect (package 'activated)
+ (setup-test 'test-dir 'tarty)
+ (package-download tarty)
+ (package-install tarty)
+ (package-status tarty))
+ (expect (package 'activated)
+ (setup-test 'test-dir 'tarty)
+ (package-download tarty)
+ (package-install tarty)
+ (package-status (car (package-find 'tarty))))
(desc "package-menu-column-offset")
(expect 0
View
@@ -1088,8 +1088,7 @@ Interactively, prompts for the package name."
(package-compute-transaction (list pkg)
(package-requires-hard pkg))))
(package-download-transaction transaction)))
- ;; Try to activate it.
- (package-initialize))
+ (package-activate pkg))
(defun package-from-single-buffer (buf)
"Create a package structure from BUF.

0 comments on commit b69b25e

Please sign in to comment.