From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Go packaging Date: Thu, 5 Oct 2017 08:16:21 -0400 Message-ID: <20171005121621.GA21466@jasmine.lan> References: <20171003151504.GA27166@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54702) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e055G-0003ps-H0 for guix-devel@gnu.org; Thu, 05 Oct 2017 08:17:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e055D-0002Hh-A0 for guix-devel@gnu.org; Thu, 05 Oct 2017 08:16:58 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:35683) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1e055D-0002HX-3K for guix-devel@gnu.org; Thu, 05 Oct 2017 08:16:55 -0400 Received: from localhost (static-63-131-119-230.ngn.onecommunications.net [63.131.119.230]) by mail.messagingengine.com (Postfix) with ESMTPA id 2B60324969 for ; Thu, 5 Oct 2017 08:16:53 -0400 (EDT) Content-Disposition: inline In-Reply-To: <20171003151504.GA27166@jasmine.lan> 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: guix-devel@gnu.org --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Oct 03, 2017 at 11:15:04AM -0400, Leo Famulari wrote: > Based on my work creating a go-build-system and packaging a non-trivial > Go application [0], I want to start a discussion on how we can > efficiently package Go software in Guix. Another question, which is bikesheddy, is how to name Go packages in Guix. So far, I've used "golang-$upstreamname", which is how Petter named the work-in-progress packages I am finishing. This leads to very long package names, but I don't know a better way to ensure unique names for each package. I think we should do "go-$upstreamname" instead. Golang is not the name of the language, but rather the domain name (go.org was apparently not available), and a term that has been adopted by the community. But, it would be good to save 4 characters here. --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlnWIpQACgkQJkb6MLrK fwhm+xAAon2ctY13h23STRuXmz1f8jihXmIEHMiYux9Pe5lynM12KYtstgagNzsW xhvnsER8eMmrASMaeh04cAoUBuI0kUML/nsapUQ36Da3SkIZvxgHqNBIF5F0OZ+H e/qcp9pglH/m/A7qDw+DaMjvIItEcQ/dRb+MMXq9OwYrMyT5dKXA+j1aqcimTbzM KlVTbWRFZipLf9Czq7wdpKWD5mxq+elVlvbiH4Vrmsu1cV3eBY63jPdpi3WzxGtq p4tq8opehop6RD3G9x4eskcrtBeQ7U+Wh4i3PKKZcpABp6pCaXFhUKFSyiA6AhEs 7vdRFSetSD/xZ1RtpEzOwZwDt67sswAxyw1qVZ5E2obfgc7mwMzi+FKfehTD/p+C j5KAeNOTYJRYMZ4kEIYmGsObgY4srIDI+OQlArpOsrQTMCptUAXMHGuGHXRJk0f0 lHbv5JbVhlsQTwC0E8ENJbgQma6tarfcLOa+6yMKtbQPiZXwlXMivarBfANhRdJI sPiliv4BdkypuPDIV/ySusArLs0Kacj+5SedhF4L2XhMLhLdyih0SsXM+kClyzJB jfcJh64HdvH1dquac4L2VyIixJLKl2booa5riDDmkAnIiATjrKtAN+kbrRvU9PRD vyDPlp+db7qgMTP5X281cbf1eMBklzBg0RyeXNOV4XKQiZyC0GM= =rxq7 -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--