Re: How to update core extensions (Gnus)?

Re: How to update core extensions (Gnus)?

[Emanuel Berg]

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?

You know what they say in Barcelona: If you ever so
slightly considered taking a psychedelic drug - you
are thinking, "well, maybe" - then you should do it :)

I hope and think Gnus isn't stagnating. Gnus is part
of Emacs (it says "Version: 5.13" in gnus.el) so you
should get updates automagically with the next version
of Emacs.

What gnus.el version do you have? You can also echo
the `gnus-version' variable.

By the way, this is your second question about getting
the latest stuff in unorthodox ways. And you even use
Emacs 25.0 (I have 24.4). You are not neurotic about
this, now? :)

-- 
underground experts united

Re: How to update core extensions (Gnus)?

[Tory S. Anderson]

Thanks. I hope I'm not neurotic about it now :) I find that lately I've been in contact with developers of several of these extensions, and so I want to be able to test their fixes/improvements as soon as they mention they've updated the codebase.

Emanuel Berg <embe8573@student.uu.se> writes:

> 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?
>
> You know what they say in Barcelona: If you ever so
> slightly considered taking a psychedelic drug - you
> are thinking, "well, maybe" - then you should do it :)
>
> I hope and think Gnus isn't stagnating. Gnus is part
> of Emacs (it says "Version: 5.13" in gnus.el) so you
> should get updates automagically with the next version
> of Emacs.
>
> What gnus.el version do you have? You can also echo
> the `gnus-version' variable.
>
> By the way, this is your second question about getting
> the latest stuff in unorthodox ways. And you even use
> Emacs 25.0 (I have 24.4). You are not neurotic about
> this, now? :)

How to update core extensions (Gnus)?

[Tory S. Anderson]

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? 

Re: How to update core extensions (Gnus)?

[Glyn Millington]

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?

Someone else may comment on that "stagnation" thing!

Yes, you can do it and if you fancy trying it you should.

Clone the repository and study the README file.

atb

Glyn

Re: How to update core extensions (Gnus)?

[Alan Schmitt]

[-- 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 --]

Re: How to update core extensions (Gnus)?

[Les Harris]

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?

As you've discovered, Gnus is pretty actively worked on.  Since you're
already running pretest builds of emacs why not just go all the way and
build the emacs git master yourself?

That way you'll get the bleeding edge stuff you want as it comes out.  I
did it for years, it is not difficult.

-- 
Do they only stand
By ignorance, is that their happy state,
The proof of their obedience and their faith?