From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Griffin Subject: Re: [PATCH] add go@1.5 Date: Tue, 12 Jul 2016 10:22:53 -0500 Message-ID: <1468336973.2793865.664073937.12E4A91D@webmail.messagingengine.com> References: <87k2gtyrtj.fsf@guixsd-mailerver.i-did-not-set--mail-host-address--so-tickle-me> <1468296701.3946941.663559065.5D0B3A3F@webmail.messagingengine.com> <87furfyyqk.fsf@guixsd-mailerver.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bMzWd-0007HD-8I for guix-devel@gnu.org; Tue, 12 Jul 2016 11:23:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bMzWY-0004BN-2e for guix-devel@gnu.org; Tue, 12 Jul 2016 11:23:06 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:47363) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bMzWV-0004Ar-Ma for guix-devel@gnu.org; Tue, 12 Jul 2016 11:23:01 -0400 In-Reply-To: <87furfyyqk.fsf@guixsd-mailerver.i-did-not-set--mail-host-address--so-tickle-me> 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: Matthew Jordan Cc: guix-devel Matthew, I don't think we should consider minimum requirements, because Go's backward compatibility is really good. I have yet to come across a package that builds with an older compiler (post-1.0) but not a newer one. Instead I think we should consider which releases we actually need and which are supported upstream. The Go Release Policy[1] says that security fixes are only issued for the current and previous releases. I had thought that the 1.5 series was EOL already but when I looked it up I guess it's still supported until next month. So I guess I don't really have any objections to packaging go 1.5, except that it should be removed next month when go 1.7 is released. Thanks, -- Alex Griffin [1]: https://golang.org/doc/devel/release.html On Tue, Jul 12, 2016, at 04:47 AM, Matthew Jordan wrote: > Good Day Alex, > > > Can I ask why even package go 1.5? Upstream has committed to making sure > > all future compiler versions can bootstrap from go 1.4.x, so my thinking > > is that we only need to package two versions, go 1.4 and the latest > > version (1.6.2 at the moment). Or am I missing something? > > Some packages still recommend building with go@1.5 or have go@1.5 as > the minimum requirement. So thought it would be a good idea to add > go@1.5 as well. > > However I have no objections towards going straight to go@1.6. > > Respectfully, > > --- > Matthew Jordan