From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?IkNsw6ltZW50IEIuIg==?= Subject: Re: Keeping up to date Date: Wed, 30 Apr 2014 19:51:39 +0200 Message-ID: <5361382B.5090805@inventati.org> References: <20140429161623.GA72660@pdavismbp15.iscinternal.com> <20140429182726.GB72660@pdavismbp15.iscinternal.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38839) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WfYfb-00085Y-Qy for emacs-orgmode@gnu.org; Wed, 30 Apr 2014 13:51:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WfYfX-00013L-2F for emacs-orgmode@gnu.org; Wed, 30 Apr 2014 13:51:47 -0400 Received: from contumacia.investici.org ([2002:b2ff:9023::1]:46416) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WfYfW-00012u-Mf for emacs-orgmode@gnu.org; Wed, 30 Apr 2014 13:51:42 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org, jw.hendy@gmail.com, pfd@pfdstudio.com Hi everyone, > So, yes, that's a bit of a headache > as well and I think if you are doing a bunch with extra Emacs add-ons, > it would be worth syncing. Rather than Dropbox, you could use a version control system. My entire=20 .emacs.d is under git control, I can try out a library, and if I like=20 it, check it in. That way, I don't really care if my elisp directory is=20 dirty, I only take home what I like. Now, that works well for lonely .el files. Two problems arise if : 1. The library is a clone of another git repository (like org) 2. The library comes from melpa (also like org) For the first one, technically, you could checkout org git repository=20 inside your .emacs, and manage it as a submodule, but they are a huge=20 pain. If you pull it out you can keep everything in sync though, and=20 still be able to play around with org branches. For the second one, melpa packages change too often to make it practical=20 to check them in. One solution is use cask, as recommended by Grant, the=20 other one (a bit more simplistic), is to make sure that the library is=20 installed on every box you use, so the sync happens at the (m)elpa=20 level. I have the following code in my init.el (it comes from emacs=20 prelude I think) : (require 'cl) (package-initialize) (add-to-list 'package-archives '("melpa" . "http://melpa.milkbox.net/packages/")) (unless package-archive-contents (package-refresh-contents) (defvar my-packages '(org auctex ess) "A list of packages to ensure are installed at launch.") (dolist (pack my-packages) (when (not (package-installed-p pack)) (package-install pack))))) This makes sure org from melpa is installed when emacs starts. It=20 doesn't check whether it's the last version though. Cl=C3=A9ment