From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [RFC] Move ox-koma-letter into core? Date: Mon, 20 Jan 2014 21:05:57 +0100 Message-ID: <874n4yju56.fsf@bzg.ath.cx> References: <878uueciku.fsf@gmail.com> <55F46D73-2430-4831-ABE9-D66AE03647E7@gmail.com> <874n50cdnu.fsf@bzg.ath.cx> <87mwisrrv8.fsf@Rainer.invalid> <87k3dwaw98.fsf@bzg.ath.cx> <87r482wo2k.fsf@Rainer.invalid> <87ha8yjzeb.fsf@bzg.ath.cx> <87eh42wju4.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56322) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W5L6n-0001WD-AK for emacs-orgmode@gnu.org; Mon, 20 Jan 2014 15:06:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W5L6g-0007MO-NK for emacs-orgmode@gnu.org; Mon, 20 Jan 2014 15:06:07 -0500 Received: from mail-wi0-x22c.google.com ([2a00:1450:400c:c05::22c]:51988) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W5L6g-0007MD-Gd for emacs-orgmode@gnu.org; Mon, 20 Jan 2014 15:06:02 -0500 Received: by mail-wi0-f172.google.com with SMTP id ex4so3617656wid.5 for ; Mon, 20 Jan 2014 12:06:01 -0800 (PST) In-Reply-To: <87eh42wju4.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 20 Jan 2014 20:10:11 +0100") 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: > So, the in-core exporters don't need to > be discovered, but the contrib exporters all need their own ELPA > package? You state it very well. In-core exporters are what people expect to be included in Emacs, easily activated without downloading and installing any new library. The contributed exporters are those that you would find by using M-x list-packages RET after adding Org ELPA. IIUC your suggestion is to keep contrib/ for things that are good candidates for core, and to remove non-candidate libraries. My suggestion is to get rid of the contrib/ directory and to have a separate Git repository with libraries available from Org ELPA. This Git repository will receive more attention that sparse code on repositories on the World Wild Web. > I understand that you want the repo split, I just don't understand > what for. To comply with the way people do use M-x list-packages RET today. -- Bastien