From: Alex Kost <alezost@gmail.com>
To: guix-devel@gnu.org
Subject: [PATCH] gnu: emacs-flycheck: Use the upstream release instead of MELPA.
Date: Tue, 01 Sep 2015 21:43:22 +0300 [thread overview]
Message-ID: <87y4gqyo8l.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Hello, ‘emacs-flycheck’ package is "broken": as you remember¹ MELPA
updates tarballs in place (“guix build --source emacs-flycheck” gives me
a different hash), so it's better to use an upstream release.
As can be seen² there is a ready-to-use tarball but only for the
previous version (0.23). There is also a snapshot of the source
code for the latest version (0.24), but it is raw:
- 'emacs-build-system' can't be used because the info manuals will not
be generated.
- 'gnu-build-system' can't be used because the provided Makefile was
created for preparing a package for Cask (not for a real installing
the package into a system).
So I took the previous release for this patch because it doesn't require
any additional tweaking.
[1] http://lists.gnu.org/archive/html/guix-devel/2015-07/msg00416.html
[2] https://github.com/flycheck/flycheck/releases
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-emacs-flycheck-Use-the-upstream-release-instead-.patch --]
[-- Type: text/x-patch, Size: 1448 bytes --]
From 7df85c9187385607f0156d82f078e1ea2c9c6162 Mon Sep 17 00:00:00 2001
From: Alex Kost <alezost@gmail.com>
Date: Tue, 1 Sep 2015 21:18:44 +0300
Subject: [PATCH] gnu: emacs-flycheck: Use the upstream release instead of
MELPA.
* gnu/packages/emacs.scm (flycheck): Change version to 0.23.
Replace MELPA tarball with the upstream release.
---
gnu/packages/emacs.scm | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index 57d45c2..594e842 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu/packages/emacs.scm
@@ -537,14 +537,15 @@ the body are let-bound and this search is done at compile time.")
(define-public flycheck
(package
(name "emacs-flycheck")
- (version "20150831.1343")
+ (version "0.23")
(source (origin
(method url-fetch)
- (uri (string-append "http://melpa.org/packages/flycheck-"
- version ".tar"))
+ (uri (string-append
+ "https://github.com/flycheck/flycheck/releases/download/"
+ version "/flycheck-" version ".tar"))
(sha256
(base32
- "0a0iyvki62rqi24dbrcdq3i1wdygdi350gcjsfrfr6fz8fasz42l"))))
+ "1n2cifzsl5dbv42l82bi3y1vk6q33msi8dd4bj7b9nvnl9jfjj5b"))))
(build-system emacs-build-system)
(propagated-inputs
`(("emacs-dash" ,emacs-dash)
--
2.4.3
next reply other threads:[~2015-09-01 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 18:43 Alex Kost [this message]
2015-09-02 13:12 ` [PATCH] gnu: emacs-flycheck: Use the upstream release instead of MELPA Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4gqyo8l.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.