I don't completely agree with this; it's better for the community to
invest in getting the ELPA packages working than for everyone to
separately work around problems by using git submodules for everything.
Yes, the rvm.el in ELPA *is* out of date; I filed a bug report offering to
help (see https://github.com/senny/rvm.el/issues/18), and the author has
lost his marmalade-repo password, so perhaps using a git version for
that package is currently advisable.
However...
Up-to-date packages for almost everything else are available in
Marmalade or ELPA, and the rinari in Marmalade is certainly the latest
version -- I uploaded it myself.
I have a reasonably complete and working Emacs configuration which
readers are welcome to look around: https://github.com/purcell/emacs.d
I used git submodules to manage package dependencies for a long time,
then el-get, and now I've invested a lot of time in packaging libraries
for ELPA -- I'd love to see the community help to move in that
direction, especially now that package.el is a standard emacs package.
-Steve
I'm sure your notes will be appreciated by many!
> Unfortunately the community uses el-get for pretty much everything
> doesn't it? I love the idea of ELPA.
It's true that many people use el-get, though I doubt it's a majority of
the community. When el-get came out, I was excited because it
seemed to be a pragmatic solution to the mess of Emacs libraries.
I contributed a lot of recipes and core patches to el-get, and
eventually concluded that it was turning into a complicated package
manager. In the meantime, the Emacs community - or at least the core
developers - had chosen a different package manager: package.el.
Encouraged by the Emacs Starter Kit author's success in splitting his
config up into separate ELPA packages, I ditched el-get, started
packaging, and now almost all of the libs I use are in ELPA; just a few
submodules remain.
Marmalade-Repo.org has some limitations, yet it still makes it
relatively easy to create packages.
I'm working on a plan to create a new package repository containing many
more ELPA packages automatically built from various emacsmirror repos
(https://github.com/emacsmirror).
So by all means use el-get if that currently lets you start doing real
work faster, but my money's on ELPA in the long term. :-)
-Steve