From: Christoph LANGE <langec@web.de>
To: John Hendy <jw.hendy@gmail.com>
Cc: Orgmode Mailing List <emacs-orgmode@gnu.org>,
Jay Kerns <gjkernsysu@gmail.com>
Subject: Re: Gentoo ebuild for app-emacs/org-mode-8.0.1
Date: Tue, 23 Apr 2013 12:54:27 +0100 [thread overview]
Message-ID: <51767673.8020008@web.de> (raw)
In-Reply-To: <CA+M2ft9WbftaxK1GVa=idLDZxhW7yaZbNNYpEuwtCu5wx9V1dA@mail.gmail.com>
2013-04-22 18:04 John Hendy:
> While Org isn't anywhere close to as messy as a LaTeX installation,
> maintaining it properly if one is planning to spread the files around
> should not be overlooked. While AUR also has an Org-mode package, I'd
> *much* rather just stick to a directory at ~/.elisp/org.git where I
> pull, make clean, make, and then simply add those dirs a the top of
> the load-path.
I think it's good to give users a choice. According to my experience,
the problem with the Gentoo org-mode package has never been that it was
poorly configured, but that it was irregularly updated. IMHO Org is
pretty much feature-complete and has a wide user base, so many users
would not want to concern themselves with "make" in a cloned git
directory to get the latest (but possibly unstable!) set of features.
I myself have installed Org from git until I learned how to write Gentoo
ebuilds. With another Emacs package (evil), I also recently switched
from git to ebuilds (maintained by someone else), because I found the
package to be sufficiently feature-complete with version 1.0.
Cheers,
Christoph
--
Christoph Lange, http://www.facebook.com/ch.lange, Skype duke4701
next prev parent reply other threads:[~2013-04-23 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 20:00 Gentoo ebuild for app-emacs/org-mode-8.0.1 Christoph LANGE
2013-04-22 16:48 ` Jay Kerns
2013-04-22 17:04 ` John Hendy
2013-04-23 11:54 ` Christoph LANGE [this message]
2013-04-22 17:21 ` Achim Gratz
2013-04-23 12:02 ` Christoph LANGE
2013-04-23 17:17 ` Achim Gratz
2013-05-03 13:03 ` Christoph LANGE
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=51767673.8020008@web.de \
--to=langec@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=gjkernsysu@gmail.com \
--cc=jw.hendy@gmail.com \
/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).