From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PATCH] gnu: vim: Update to 8.0.0047. Date: Fri, 28 Oct 2016 07:19:09 +0000 Message-ID: <87oa259c0i.fsf@we.make.ritual.n0.is> References: <87y419zzs1.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> <87insdf1ta.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44584) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c01SE-00010D-Bs for guix-devel@gnu.org; Fri, 28 Oct 2016 03:19:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c01SA-0004G4-B4 for guix-devel@gnu.org; Fri, 28 Oct 2016 03:19:54 -0400 Received: from aibo.runbox.com ([91.220.196.211]:35015) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c01SA-0004Dq-4C for guix-devel@gnu.org; Fri, 28 Oct 2016 03:19:50 -0400 In-Reply-To: <87insdf1ta.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 28 Oct 2016 08:02:57 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org Ricardo Wurmus writes: > Marius Bakke 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