From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Consolidating Go packages Date: Thu, 15 Aug 2019 14:40:58 -0400 Message-ID: <20190815184058.GA24201@jasmine.lan> References: <20190814190617.GA30864@jasmine.lan> <20190815081906.GA27046@E2140> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38731) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hyKgS-0004by-6i for guix-devel@gnu.org; Thu, 15 Aug 2019 14:41:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hyKgP-0004cq-PO for guix-devel@gnu.org; Thu, 15 Aug 2019 14:41:12 -0400 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]:52685) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hyKgP-0004YY-Cw for guix-devel@gnu.org; Thu, 15 Aug 2019 14:41:09 -0400 Content-Disposition: inline In-Reply-To: <20190815081906.GA27046@E2140> 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: Efraim Flashner Cc: guix-devel@gnu.org On Thu, Aug 15, 2019 at 11:19:06AM +0300, Efraim Flashner wrote: > So to summarize, while it is techincally possible to "build" them, in > actuality they are used in source code form as part of the build > process. That's true for Guix but not if you were building Go software outside of Guix. In that case they would be compiled and re-used through the use of Go's built-in memoized cache (it's very similar to what Guix does). It's basically a limitation or bug in our go-build-system that re-using compiled Go objects does not work. > So, either it should be just a "source snippet" or it should be a hidden > package. Nobody needs to install these libraries but they should be packages so they show up in the Guix UI (`guix package --show`). I think we can treat them like other shared library packages. And there is currently some "building" from our point of view =E2=80=94 a package-specific filesys= tem hierarchy is created.