emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: mattcto@Safe-mail.net
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode on GNU ELPA
Date: Fri, 15 Jul 2011 11:46:46 +0530	[thread overview]
Message-ID: <81k4bk9igh.fsf@gmail.com> (raw)
In-Reply-To: <N1-ATUUyI4gxo@Safe-mail.net> (mattcto@safe-mail.net's message of "Wed, 13 Jul 2011 12:08:25 -0400")

mattcto@Safe-mail.net writes:

> Org-mode on GNU ELPA does not distribute the contrib-directory. Is
> there any chance this could be added?

I have a patch to Makefile which permits this to be done. I have not
been able to spend much time hacking for the last week or so but I plan
to nudge it forward as soon as my spirit is willing.

The actual inclusion of specific items would be governed by GNU ELPA's
policy. Since you use the term 'GNU ELPA' I believe you are following at
the discussions on the emacs-devel list.

The ELPA tarball contains no other documentation apart from the info
file. Would you also like to see the html, pdf documentation and
refcards be distributed with?

What files in the contrib dir are you interested in? If indicate your
preferences, may be this discussion wouldn't end up being too abstract.

> Other than that, I think the GNU ELPA archive is synced with the
> trunk/master rather than with the actual releases.


> 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?

From the Org side of things, there are discussions about having a stable
and devel branches - I think they are called master and maint.

From the package manager of things, the archive-contents file which is a
"catalogue" for the packages distributed by the repo, permit only ONE
latest version for a package. The problem really is that there are could
potentially TWO latest versions of a package - a development version
that is a daily snapshot and a stable release (What is "latest", is
defined by the user preferences) - and BOTH of them cannot be
distributed in existing scheme of things. ie., you either have latest
devel or the latest stable but not both.

You can refer to my Oct 2010, post on emacs-devel for further


The post didn't gain much traction. I think my idea were perhaps too
early for it's time (Atleast that's what I would like to believe in)

Jambunathan K.


  reply	other threads:[~2011-07-15  6:16 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 [this message]
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

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:

  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=81k4bk9igh.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mattcto@Safe-mail.net \


* 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).