unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Morgan Smith <Morgan.J.Smith@outlook.com>
Cc: 43910@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#43910] [PATCH] gnu: emacs-modus-vivendi-theme: Update to 0.13.0.
Date: Mon, 02 Nov 2020 19:33:39 +0100	[thread overview]
Message-ID: <87h7q7mwvw.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <DM5PR1001MB21052C65378C0A8A80F4A3FCC5100@DM5PR1001MB2105.namprd10.prod.outlook.com> (Morgan Smith's message of "Mon, 2 Nov 2020 09:19:18 -0500")

Hello,

Morgan Smith <Morgan.J.Smith@outlook.com> writes:

> If we do really want to keep using elpa (someone please explain to me
> the benefits of doing this) than the good news is the author is working
> on it and we just have to be patient. The moment this link says 0.13
> instead of 0.12, we can do a version bump:
> https://elpa.gnu.org/packages/modus-operandi-theme.html

GNU ELPA is preferred because updating the package is much easier. This
is important when you have lot of packages you want to keep up-to-date.
It is also easier to get notified about updates, but that's not specific
to Guix.

Usually, GNU ELPA catches up releases quickly, but it seems more
complicated in this case. So, I think it is reasonable to update this
package using GitHub source and switch back to ELPA when the situation
is sorted out.

Regards,

-- 
Nicolas Goaziou




  reply	other threads:[~2020-11-02 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10 16:00 [bug#43910] [PATCH] gnu: emacs-modus-vivendi-theme: Update to 0.13.0 Morgan.J.Smith
2020-10-11 16:25 ` Nicolas Goaziou
2020-10-11 16:33   ` Morgan Smith
2020-11-02 13:50     ` Ludovic Courtès
2020-11-02 14:19       ` Morgan Smith
2020-11-02 18:33         ` Nicolas Goaziou [this message]
2020-10-30 18:16 ` [bug#43910] (no subject) André Alexandre Gomes
2020-10-31  5:07 ` [bug#43910] [PATCH] gnu: emacs-modus-vivendi-theme: Update to 0.13.0 Protesilaos Stavrou
2020-11-03 11:01 ` bug#43910: " Nicolas Goaziou

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7q7mwvw.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=43910@debbugs.gnu.org \
    --cc=Morgan.J.Smith@outlook.com \
    --cc=ludo@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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.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).