From debbugs-submit-bounces@debbugs.gnu.org Wed Feb 03 18:54:13 2021 Received: (at 45476) by debbugs.gnu.org; 3 Feb 2021 23:54:13 +0000 Received: from localhost ([127.0.0.1]:39204 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l7RyP-0002Jb-Hp for submit@debbugs.gnu.org; Wed, 03 Feb 2021 18:54:13 -0500 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:39919) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l7RyN-0002JM-Vs for 45476@debbugs.gnu.org; Wed, 03 Feb 2021 18:54:12 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id C00E2D58; Wed, 3 Feb 2021 18:54:05 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 03 Feb 2021 18:54:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=famulari.name; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=mesmtp; bh=+WaK1WTmJt1pQzDkij7n878YgfJnmDBee3GIbwPgVTs=; b=dFmtgDVhXGi4 /vZAqPyLp+kJxms4kxgCp7YkehaCZ2NJiEn9c/4gcIomK9R2LbhKn1dVBaBll43p x6C073FvRhnLSePkD8PXFz82KQI4odyoITruyD1QFimlRWYn7XxjdAu53Cd7RGFa cfXkbDB7NiDGLJWrufl8Mgw/YEmcyc0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=+WaK1WTmJt1pQzDkij7n878YgfJnmDBee3GIbwPgV Ts=; b=LJQACHnpqlX5o0Ms9p1MayssA8mTPkpc1IfTGJlYB1HoN8yi5yZxdHefA 8ctB+ERATBGL9WlNUviHv/de36uMkFPoQaDGyGstVU2QD9ZpBDQz3VnZ4fceIm6s KzrCcC3DuqtzhQlqLOOMlQ+6j47fn4ec+WvEaYuOW7rkJaMtzkBePOL1ZfFWtuxm l0vXxCz00LgYvDlR+2Y6GLslBhFJv1JTyr2fD4piypHreBtWnW3E3WaaF9v6WEsb saSJerJ5P07XkfQIXyRLkC7RV1dniecE3DdhNnhVHcEBUyeM+vTugaiiZ7Wm1c5V Be81VLw1OObKV0vp2HLL/JrJ6mrDg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrgeefgddutdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggugfgjsehtkeertddttdejnecuhfhrohhmpefnvghoucfh rghmuhhlrghrihcuoehlvghosehfrghmuhhlrghrihdrnhgrmhgvqeenucggtffrrghtth gvrhhnpeegjeeggeehtddugfffuddtvdfffeffjeekffffveffheegvddvuedtffekjeej jeenucfkphepuddttddruddurdduieelrdduudeknecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomheplhgvohesfhgrmhhulhgrrhhirdhnrghmvg X-ME-Proxy: Received: from localhost (pool-100-11-169-118.phlapa.fios.verizon.net [100.11.169.118]) by mail.messagingengine.com (Postfix) with ESMTPA id 99DF6108005B; Wed, 3 Feb 2021 18:54:04 -0500 (EST) Date: Wed, 3 Feb 2021 18:54:02 -0500 From: Leo Famulari To: Ludovic =?iso-8859-1?Q?Court=E8s?= Subject: Re: bug#45476: [PATCH] gnu: syncthing: Update to 1.12.0. Message-ID: References: <20201227212304.19409-1-dftxbs3e@free.fr> <20201227220016.20897-1-dftxbs3e@free.fr> <87sg7498mr.fsf_-_@gnu.org> <87ft3368s3.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87ft3368s3.fsf@gnu.org> X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 45476 Cc: John Doe , 45476@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) On Thu, Jan 14, 2021 at 12:46:20PM +0100, Ludovic Courtès wrote: > Leo Famulari skribis: > > However, the mechanisms used to build Syncthing (and to build Go > > software in general) have changed since that work was done, and the > > go-build-system we have can no longer build recent versions of Syncthing > > except by using the bundled source code. > > But it can build this older version of Syncthing. What’s fundamentally > different between the way the old and the new version of Syncthing are > built? Basically, the Go language introduced a memoized cache for dependency management. Yes, just like Guix and Nix. More generally, "things changed" and the highly-choreographed orchestration of the old-style Go build tools in go-build-system.scm no longer works for Syncthing's dependencies, for some reason. Important to note: Go integrates dependency management, compilation, and deployment. > > We need to overhaul the go-build-system if we want to continue offering > > unbundled Go packages. > > Could you explain what needs to be done? Perhaps starting a new thread > on guix-devel, with an eye on recruiting interested hackers. :-) Sorry for the slow reply. I really ran out of energy for Go in Guix. As for this question, in the past I learned the answer and wrote it, somewhere in the Guix mailing lists. If I remember where, I'll reply with a link. But, it's a good time for us to nurture the next generation of Guix hackers who know about Go.