unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: vim: Update to 8.0.0047.
Date: Fri, 28 Oct 2016 07:19:09 +0000	[thread overview]
Message-ID: <87oa259c0i.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87insdf1ta.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 28 Oct 2016 08:02:57 +0200")

Ricardo Wurmus <rekado@elephly.net> writes:

> 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?
>
> I’m also not happy about using a third-party mirror for vim.  Can we be
> sure that this is updated consistently and in time?  (Is this done
> automatically?)
>
> Guix can handle downloading patches, so there’s really no need for
> switching in my opinion.  “gnu/packages/bash.scm” could be used as a
> reference for how to deal with a large number of patches.
>
> ~~ Ricardo

Last time I looked at the method used in bash.scm it was not
obvious how the method should be used, and from my impression in
irc it wasn't obvious to others when they tried to update bash or
what it was.

If vim gets an equal method, can we please document how the
patches are downloaded (in other words: how you execute the
download of scripts to store) in the module(s) or somewhere else?

In addition to my first message: I think we should not rely too
much on github.com, when it goes down again we have no fallback
solution.
-- 
♥Ⓐ  ng0  | ng0.chaosnet.org

  reply	other threads:[~2016-10-28  7:19 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
2016-10-28  6:02 ` Ricardo Wurmus
2016-10-28  7:19   ` ng0 [this message]
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

  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=87oa259c0i.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).