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, 13 Jan 2021 15:49:18 -0500 [thread overview]
Message-ID: <X/9czkEN+LiD9Kpu@jasmine.lan> (raw)
In-Reply-To: <87sg7498mr.fsf_-_@gnu.org>
On Wed, Jan 13, 2021 at 04:09:00PM +0100, Ludovic Courtès wrote:
> > * gnu/packages/syncthing.scm (syncthing): Update to 1.12.0.
> > [source]: Do not delete bundled dependencies, maintaining the
> > syncthing package without them is too much trouble. Syncthing's upstream
> > seems committed to including only Free Software in their releases.
>
> A large part of the hard unbundling work was already done, though, so
> intuitively I think we should not lose it. Leo, WDYT?
That's correct.
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.
We need to overhaul the go-build-system if we want to continue offering
unbundled Go packages. I have not found the time to work on this. If
anyone is interested in supporting this work, please get in touch! And
of course, if anyone is interesting in *doing* the work, that's great
too :) I will be happy to offer advice and help test.
In the absence of a new go-build-system, it's hard to decide what to do
here.
next prev parent reply other threads:[~2021-01-13 20: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 [this message]
2021-01-14 11:46 ` Ludovic Courtès
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
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=X/9czkEN+LiD9Kpu@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).