all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: John Doe <dftxbs3e@free.fr>, 45476@debbugs.gnu.org
Subject: [bug#45476] [PATCH] gnu: syncthing: Update to 1.12.0.
Date: Thu, 14 Jan 2021 12:46:20 +0100	[thread overview]
Message-ID: <87ft3368s3.fsf@gnu.org> (raw)
In-Reply-To: <X/9czkEN+LiD9Kpu@jasmine.lan> (Leo Famulari's message of "Wed, 13 Jan 2021 15:49:18 -0500")

Hi,

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?

> 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.  :-)

> In the absence of a new go-build-system, it's hard to decide what to do
> here.

I suppose it depends in part on the amount of work needed to keep
using unbundled libraries.

Thanks,
Ludo’.




  reply	other threads:[~2021-01-14 11:51 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 [this message]
2021-02-03 23:54         ` Leo Famulari
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

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

  git send-email \
    --in-reply-to=87ft3368s3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=45476@debbugs.gnu.org \
    --cc=dftxbs3e@free.fr \
    --cc=leo@famulari.name \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.