EDIT 07/01/2014: I don’t recommend setting up packages like this anymore. I recommend reading
this post instead
About a year ago I wrote about installing packages on startup, automatically for Emacs 24. This used the native ELPA, looked for packages that weren’t already installed, and used package-install to install them.
Unfortunately, I realized that this method wasn’t nearly as functional as I wanted it to be. I’ll save my opinions for later. If you’re just looking for a great way to install packages for Emacs, I’ll just write it out here.
What I do
Here’s a baseline example of how to manage your packages:
What does this do? Well:
- Checks for installation of el-get, my package manager of choice, and installs it if one doesn’t exist
- Sets a list of package definitions into el-get-sources
- Looks through the whole list of el-get-sources, ad runs el-get-install if the package isn’t installed (verified via the ‘require’ command)
If I find a new package I want, whether it’s on github, elpa, or
otherwise, I first check if the package info already exists in
el-get’s huge list of recipes, or I write
it up myself. As an example, install an elpa package is as simple as:
(:name rainbow-mode :type elpa)
How about a git repository? In that case it’s just:
(:name scala-mode :type git :url "http://github.com/scala/scala-dist.git")
Or a shortened github version:
(:name scala-mode :type github :pkgname "scala/scala-dist.git")
Also in my system, I put my el-get-sources list into a different file and load it, it makes it way easier to manager than a huge chunk of data halfway through a bunch of code:
;; e.g. put the "el-get-sources" list in .emacs.elgetpackages (load "~/.emacs.d/.emacs.elgetpackages")
Try it out for yourself! Watch as all of your favorite packages get installed on startup. Note that the install order might be different, as the cloning and installing process is performed asynchronously.
Why I do it this way
So why do I el-get now instead of package.el and ELPA?
When I started using ELPA. I was really satisfied. It was so easy to find and discover new packages, and installing them was a snap! However, with the rate at which emacs plugin development occurs, the packages are outdated quickly. In the world of github, and an incredibly active community, I found that my main issue was being able to install the most recent version of packages out there, and keeping them up to date.
ELPA is only as up to date as the package developers make it, and depending on the library, that’s not a lot. In addition, there are quite a lot of libraries out there which haven’t made it yet into a package.el repository.
So why wait? When adding a new package to your distributable emacs configuration is one line away, you don’t have to.
el-get provides basically everything I’m looking for:
- a specific ‘github’ type for github repos. An absolute necessity, a lot of really good emacs extensions are on github.
- generic git cloning. Great for the other libraries stores elsewhere
- it even hooks into elpa for other packages!
Although I rarely use package.el or ELPA anymore. If I can find the github equivalent, I’ll use that instead. You’d be surprised how outdated existing libraries become.
This also provides the flexibility of allowing me to use my own version of various libraries, if need be. I no longer have to wait for pull requests to enjoy my fixes: I can just use my own repository, and switch back when the main repository catches up.
So if you want to stay on the cutting-edge, and not worry about the hassle of installing every single package you use on every machine you have, give this a shot.