el-get-sources is just another recipe source
Dimitri Fontaine <dim@...
2011-06-22 21:02:18 GMT
After some more pondering about it, I've recently pushed a series of
changes in el-get. The main commit would be the following:
Author: Dimitri Fontaine <dim@...>
Date: Wed Jun 22 11:38:40 2011 +0200
`el-get' now defaults to caring about packages known "required" and "installed" from the status file.
This should bring a much easier to understand semantics, near of that of
apt-get and friends: by default, any installed package is automatically
initialized at next startup without special care. If you don't need local
recipes, you don't need to edit and maintain any `el-get-sources'.
It's still possible to manually prepare a list of packages to install, so
that you can share your setup between multiple installations. To do that,
give the package list (names or symbols) to the (el-get) call in your setup.
This way you can also maintain specific lists depending on system or network
or whatever is useful for you. That's the advanced setup, documented.
That means that I believe the problem and difficulties reported by
Richard are now solved, in a way that still allow advanced users to
still be able to sync several Emacs installations.
Basic usage involves caring about the load-path to be able to require
el-get and then place a call to (el-get 'sync), and that's about it.
You install packages using M-x el-get-install, you restart Emacs and
there you go.
But if you want to share the package list then you might need something
a little more involved. Here's what the emacs-kicker is now looking
;; set local recipes
:after (lambda ()
(global-set-key (kbd "C-x C-z") 'magit-status)))))
;; now set our own packages
(setq my:el-get-packages '(el-get escreen ...))
(loop for src in el-get-sources collect (el-get-source-name src))))
;; install new packages and init already installed packages
(el-get 'sync my:el-get-packages)
To unsubscribe, send mail to el-get-devel-unsubscribe@...