From: ng0 <ng0@we.make.ritual.n0.is>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: vim: Update to 8.0.0047.
Date: Thu, 27 Oct 2016 20:20:33 +0000 [thread overview]
Message-ID: <87k2ct4k8e.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87y419zzs1.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Thu, 27 Oct 2016 14:29:02 +0100")
Marius Bakke <mbakke@fastmail.com> writes:
> The official vim mirrors only carries major versions and individual
> patches, no up-to-date releases. This patch changes the source uri to
> the tagged github releases instead of downloading all 40+ (so far)
> patches individually.
>
> I'm not very happy about changing to a third-party source, but IMO it
> beats keeping track of the frequent patches. WDYT?
Someone (you?) previously told me that this is not third-party
but encouraged source by upstream itself. My other system
(Gentoo) pulls vim from github aswell so this seems okay. I guess
more systems do it this way.
> From 786dc474126431c8d2b9b97644dd629f5f7aed37 Mon Sep 17 00:00:00 2001
> From: Marius Bakke <mbakke@fastmail.com>
> Date: Thu, 27 Oct 2016 14:14:40 +0100
> Subject: [PATCH] gnu: vim: Update to 8.0.0047.
>
> * gnu/packages/vim.scm (vim): Update to 8.0.0047.
> [source]: Change to github release archive.
> ---
> gnu/packages/vim.scm | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
> index 4ee8c7d..32f9e62 100644
> --- a/gnu/packages/vim.scm
> +++ b/gnu/packages/vim.scm
> @@ -48,14 +48,15 @@
> (define-public vim
> (package
> (name "vim")
> - (version "8.0")
> + (version "8.0.0047")
> (source (origin
> (method url-fetch)
> - (uri (string-append "ftp://ftp.vim.org/pub/vim/unix/vim-"
> - version ".tar.bz2"))
> + (uri (string-append "https://github.com/vim/vim/archive/v"
> + version ".tar.gz"))
> + (file-name (string-append name "-" version ".tar.gz"))
> (sha256
> (base32
> - "1s34rf8089klsbdx5l0iw7vjymir0kzfrx8wb30s31wygnq29axc"))))
> + "1l24pbc06970crk513a98vlr77sp6wq6d0ylviwk9nhvfz4p0cff"))))
> (build-system gnu-build-system)
> (arguments
> `(#:test-target "test"
--
♥Ⓐ ng0 | ng0.chaosnet.org
next prev parent reply other threads:[~2016-10-27 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 13:29 [PATCH] gnu: vim: Update to 8.0.0047 Marius Bakke
2016-10-27 20:20 ` ng0 [this message]
2016-10-28 6:02 ` Ricardo Wurmus
2016-10-28 7:19 ` ng0
2016-10-28 16:55 ` Marius Bakke
2016-10-28 17:12 ` Ricardo Wurmus
2016-10-28 19:57 ` Marius Bakke
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=87k2ct4k8e.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.