From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to update core extensions (Gnus)?
Date: Mon, 02 Mar 2015 13:52:41 +0100 [thread overview]
Message-ID: <m2h9u3pnmu.fsf@polytechnique.org> (raw)
In-Reply-To: 87wq2z610j.fsf@gmail.com
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On 2015-03-02 07:23, torys.anderson@gmail.com (Tory S. Anderson) writes:
> Contrary to my long-held belief in the stagnation of the Gnus codebase
> (I was under the impression it had been untouched since 2009), Gnus
> has been revived and I want to implement changes that are newer than
> my current 25.0.5 emacs version. But it looks from my package manager
> that Gnus isn't something that I can, for instance, grab from
> Melpa. What's the best practice for updating a core package like this?
> Can I clone http://git.gnus.org/gnus.git and cause emacs to respect
> the clone over the built-in? Should I?
I use the git version of gnus. I simply do "make" after checking it out,
then I have this in my init.el:
#+begin_src emacs-lisp
(add-to-list 'load-path "~/src/gnus/lisp/")
(require 'gnus-load)
#+end_src
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2015-03-02 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 12:23 How to update core extensions (Gnus)? Tory S. Anderson
2015-03-02 12:39 ` Glyn Millington
2015-03-02 12:52 ` Alan Schmitt [this message]
2015-03-03 1:34 ` Les Harris
[not found] <mailman.1130.1425299050.31049.help-gnu-emacs@gnu.org>
2015-03-02 23:34 ` Emanuel Berg
2015-03-03 19:06 ` Tory S. Anderson
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2h9u3pnmu.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=help-gnu-emacs@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.
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).