From: Bastien <email@example.com>
Subject: Re: Org-mode on GNU ELPA
Date: Sat, 16 Jul 2011 13:06:18 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <N1-ATUUyI4gxo@Safe-mail.net> (email@example.com's message of "Wed, 13 Jul 2011 12:08:25 -0400")
> Org-mode on GNU ELPA does not distribute the contrib-directory. Is there
> any chance this could be added?
No, because the GNU ELPA policy requires that the authors of a GNU ELPA
file sign the FSF assignment.
One of the reasons we have a contrib/ directory is that we don't want to
limit Org's distribution to files from authors who signed this agreement.
> Other than that, I think the GNU ELPA
> archive is synced with the trunk/master rather than with the actual
> I often encounter minor bugs when working with org which usually
> disappear after updating from GNU ELPA again. Is is possible that the
> mainline release (7.6) is distributed via ELPA rather than a bleeding edge
> development version?
The main reason we have an Org tarball in GNU ELPA is to let users
easily access to the bleeding edge version of Org. If GNU ELPA contains
the exact same version than Emacs, then there is no real advantage of
distributing Org in both channels. So I think it's better to stick to
the current scheme.
prev parent reply other threads:[~2011-07-16 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 16:08 Org-mode on GNU ELPA mattcto
2011-07-15 6:16 ` Jambunathan K
2011-07-16 10:58 ` Bastien
2011-07-16 12:53 ` Jambunathan K
2011-07-16 13:03 ` Bastien
2011-07-16 11:06 ` Bastien [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).