From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike McLean Subject: Re: Makefile restructuring Date: Mon, 23 Apr 2012 21:46:59 -0400 Message-ID: <0B99052C-9B74-4C64-BA0B-F62D832E1260@pobox.com> References: <87k4bqwkyw.fsf@gnu.org> <87sjqejvob.fsf@Rainer.invalid> <87k4bqjnwu.fsf@Rainer.invalid> <87fwmdkind.fsf@Rainer.invalid> <874o2t81qu.fsf@gnu.org> <87liw43iys.fsf@Rainer.invalid> <8762n8d4ys.fsf@gnu.org> <87ei1u6u3q.fsf_-_@Rainer.invalid> <87hb6i3z1l.fsf@Rainer.invalid> <87k47av6j2.fsf@Rainer.invalid> <87fwhyux4d.fsf@Rainer.invalid> <87397x1i8u.fsf@altern.org> <87bomldxn4.fsf@Rainer.invalid> <874nsdduhh.fsf@Rainer.invalid> <878vhnixv0.fsf@Rainer.invalid> Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38830) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SMUqT-0005tm-QS for emacs-orgmode@gnu.org; Mon, 23 Apr 2012 21:47:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SMUqR-0001yk-GC for emacs-orgmode@gnu.org; Mon, 23 Apr 2012 21:47:09 -0400 Received: from a-pb-sasl-sd.pobox.com ([74.115.168.62]:52245 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SMUqR-0001xZ-7J for emacs-orgmode@gnu.org; Mon, 23 Apr 2012 21:47:07 -0400 In-Reply-To: <878vhnixv0.fsf@Rainer.invalid> 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: Achim Gratz Cc: org-mode mailing list On Apr 22, 2012, at 11:34 AM, Achim Gratz wrote: > suvayu ali writes: >> The above recipe works. But just "make", leaves the working tree = without >> lisp/org-install.el. =46rom the log I see it explicitly deletes it, = but >> doesn't generate it again. A subsequent "make autoloads" is required = to >> get a working org setup. Is this expected behaviour? >=20 > This is intentional. The autoloads are generated just before > installing, since that's where they are needed. I really don't want = to > encourage further use of the git worktree as the "org installation", > although it sort of works if you do a "make auto loads". This makes sense, and I=92ve asked the question on how best to handle = for el-get on Gihub. Meanwhile my original pull request has been merged, = so for the moment at least el-get uses the ("compile" "autoloads" = "info") workflow. You are correct that adding a make autoloads does = work, I've used (and updated) compiled org-mode straight from the work = tree for a few days now. If there is a better or more canonical way to = do this, I'd be happy to change and work the changes back into el-get = where I can. > You can now easily keep multiple installations within the org = directory > if so desired (I do this myself for testing). Using the worktree > instead can lead to very hard to track bugs when the autoload files = get > out of sync with the sources. This is the reason I always remove them > before compilation and I should probably remove them just after > installation as well. What do you do to make that work? It sounds like an intriguing = possibility.