From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Org-mode release 7.9 Date: Tue, 18 Sep 2012 06:31:06 -0600 Message-ID: <87fw6fzf5h.fsf@gmx.com> References: <87sjbcb89x.fsf@altern.org> <87sjb9iqgp.fsf@Rainer.invalid> <878vcylxi7.fsf@Rainer.invalid> <873935mvd9.fsf@altern.org> <20120829234032.GA27761@panix.com> <878vcxgcdz.fsf@altern.org> <87sjb4725t.fsf@Rainer.invalid> <878vcwmdne.fsf@gmx.com> <87fw73v74v.fsf@altern.org> <87pq67uev7.fsf@Rainer.invalid> <87boho4ph2.fsf@altern.org> <87627n8owx.fsf@Rainer.invalid> <87d31p5dm1.fsf@altern.org> <877grvjgkk.fsf@Rainer.invalid> <87pq5nm5f9.fsf@gmx.com> <87y5kbhwju.fsf@Rainer.invalid> <87392i9hd3.fsf@gmx.com> <874nmy3scb.fsf@Rainer.invalid> <87haqwpn47.fsf@gmx.com> <87wqzsa4d4.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TDwzK-0003Ff-U6 for emacs-orgmode@gnu.org; Tue, 18 Sep 2012 08:33:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TDwzH-0008Ls-6L for emacs-orgmode@gnu.org; Tue, 18 Sep 2012 08:33:14 -0400 Received: from mailout-eu.gmx.com ([213.165.64.43]:35067) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1TDwzG-0008Fl-T9 for emacs-orgmode@gnu.org; Tue, 18 Sep 2012 08:33:11 -0400 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: emacs-orgmode@gnu.org Achim Gratz writes: > Eric Schulte writes: >> Agreed, this would simply mean generating an archive-contents file on >> the Org-mode site which lists the latest org and orgplus archive. I'm >> not sure which elisp function is used to generate this file, but it >> could be done directly from the server.mk file with something like... >> >> # -*- Makefile -*- >> archive-contents: >> echo "(1 (org . [($(PKG_TAG)) nil \"$(PKG_DOC)\"])" > $<; \ >> echo " (orgplus . [($(PKG_TAG)) nil \"$(PKG_DOC)\"]))" > $<; > > No, you'd need ">>" on the second line. > Yup, good catch. > > BTW, I'm going to revert your change for removing PGK_REQ since you've > done it in the wrong branch. I'd like to keep the PKG_REQ variable for > possible future use, can you please test if the package archives that > choke on nil can correctly deal with "()" or "(())"? Otherwise I'd > leave the variable undefined, which results in the same thing as your > patch. > Please do go ahead and revert that commit. If we're hosting our own packages on orgmode.org, then I don't think we need to worry about conforming to the vagaries of other ELPA package parsers (in this case marmalade). I do think that leaving PKG_REQ undefined when there are no dependencies is the best of the options listed above. Thanks, > > > Regards, > Achim. -- Eric Schulte http://cs.unm.edu/~eschulte