unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: John Doe <dftxbs3e@free.fr>, 45476@debbugs.gnu.org
Subject: [bug#45476] [PATCH] gnu: syncthing: Update to 1.12.0.
Date: Wed, 3 Feb 2021 18:54:02 -0500	[thread overview]
Message-ID: <YBs3mj+oe1Bk2eoj@jasmine.lan> (raw)
In-Reply-To: <87ft3368s3.fsf@gnu.org>

On Thu, Jan 14, 2021 at 12:46:20PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> 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.




  reply	other threads:[~2021-02-03 23:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-27 21:23 [bug#45476] [PATCH] gnu: syncthing: Update to 1.12.0 John Doe
2020-12-27 22:00 ` [bug#45476] [PATCH v2] " John Doe
2021-01-13 15:09   ` [bug#45476] [PATCH] " Ludovic Courtès
2021-01-13 20:49     ` Leo Famulari
2021-01-14 11:46       ` Ludovic Courtès
2021-02-03 23:54         ` Leo Famulari [this message]
2021-02-16  1:11 ` Tom Willemse
2021-02-16 20:50   ` Leo Famulari
2021-05-06  3:56     ` Tom Willemse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YBs3mj+oe1Bk2eoj@jasmine.lan \
    --to=leo@famulari.name \
    --cc=45476@debbugs.gnu.org \
    --cc=dftxbs3e@free.fr \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).