emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 9913@debbugs.gnu.org
Subject: bug#9913: 24.0.91; ELPA: OpenDocument Text exporter for Org
Date: Tue, 01 Nov 2011 04:04:57 +0530	[thread overview]
Message-ID: <81bosw7pta.fsf__36946.6449520134$1320100568$gmane$org@gmail.com> (raw)
In-Reply-To: <t8vcr4247m.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 31 Oct 2011 18:20:29 -0400")

Glenn Morris <rgm@gnu.org> writes:

> Jambunathan K wrote:
>
>> I would like to submit my OpenDocument Text exporter for Org to GNU ELPA.
>
> Org is already in GNU ELPA (with daily snapshots IIUC), so if your
> package is accepted into Org it will automatically be in GNU ELPA.

True. But the fact is ODT exporter is not yet part of the Org proper.

Long story:

Org's git repo has a ./lisp/ dir and a ./contrib/lisp/ dir. ODT exporter
resides in ./contrib/lisp/ and ./contrib/odt/ directories of the git
repo. Since Org's ELPA tarball contain only the main lisp files and not
contrib lisp files, ODT exporter is *not* available as part of daily
snapshots.

Here is Org's git tree for reference: 
http://orgmode.org/w/?p=org-mode.git;a=tree

  parent reply	other threads:[~2011-10-31 22:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8139e9r5v1.fsf@gmail.com>
     [not found] ` <jwvobwxl3i8.fsf-monnier+emacs@gnu.org>
2011-10-31 21:58   ` bug#9913: 24.0.91; ELPA: OpenDocument Text exporter for Org Jambunathan K
     [not found]   ` <81obwwvn5j.fsf@gmail.com>
2011-10-31 22:15     ` Jambunathan K
2011-10-31 22:20 ` Glenn Morris
     [not found] ` <t8vcr4247m.fsf@fencepost.gnu.org>
2011-10-31 22:34   ` Jambunathan K [this message]
     [not found]   ` <81bosw7pta.fsf@gmail.com>
2011-12-12  0:09     ` Glenn Morris
     [not found]     ` <qafwgqfy6j.fsf@fencepost.gnu.org>
2011-12-12  4:55       ` Jambunathan K

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='81bosw7pta.fsf__36946.6449520134$1320100568$gmane$org@gmail.com' \
    --to=kjambunathan@gmail.com \
    --cc=9913@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).