emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Jay Kerns <gjkernsysu@gmail.com>
Cc: Orgmode Mailing List <emacs-orgmode@gnu.org>,
	Christoph LANGE <langec@web.de>
Subject: Re: Gentoo ebuild for app-emacs/org-mode-8.0.1
Date: Mon, 22 Apr 2013 12:04:14 -0500	[thread overview]
Message-ID: <CA+M2ft9WbftaxK1GVa=idLDZxhW7yaZbNNYpEuwtCu5wx9V1dA@mail.gmail.com> (raw)
In-Reply-To: <CAFiLVraZBtnzd2HYCGYG3oYF-ck2MZ0oG8WbN50hJLYCv8ErEw@mail.gmail.com>

On Mon, Apr 22, 2013 at 11:48 AM, Jay Kerns <gjkernsysu@gmail.com> wrote:
> Christoph,
> On Sun, Apr 21, 2013 at 4:00 PM, Christoph LANGE <langec@web.de> wrote:
>> Hi all,
>> Gentoo users may find my ebuild for app-emacs/org-mode-8.0.1 useful.
>> Please download it from
>> https://466720.bugs.gentoo.org/attachment.cgi?id=346230 and let's hope
>> this ebuild (or alternatively Emacs 24.4) will be included with Portage
>> soon (subscribe to https://bugs.gentoo.org/show_bug.cgi?id=466720 to
>> track the progress).
>> Thanks to Bastien et al. for version 8!
>> Cheers,
>> Christoph
> Thank you for this work!  It's very helpful.  May it have a speedy
> Portage review.

As an Arch Linux user who absolutely loves the AUR and have an
appreciation for the massive number of packages available for both
Arch and Gentoo, I caution this sort of thing if not properly
maintained. As a parallel anecdote, I switched from the AUR build of
TexLive for the fact that enough locations and stale files get left
around that upgrading was giving errors and path variables weren't
pointing in the right location. Manually maintaining TexLive has
proved unbelievably easier, primarily due to being able to specify
everything in a local directory in ~/ vs. spread throughout /usr/lib,
/etc, /var, etc.

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.

Just food for thought. Again, Org might not be difficult to maintain
at all, but I've been burned in the past by some of these. Just
couldn't help making a response!

Best regards,

> Best wishes,
> --
> Jay

  reply	other threads:[~2013-04-22 17:04 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 [this message]
2013-04-23 11:54     ` Christoph LANGE
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:

  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='CA+M2ft9WbftaxK1GVa=idLDZxhW7yaZbNNYpEuwtCu5wx9V1dA@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gjkernsysu@gmail.com \
    --cc=langec@web.de \


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