On Sun, Sep 24, 2017 at 04:40:53PM -0400, Leo Famulari wrote:
> * gnu/packages/syncthing.scm: New file.
> 
> Co-authored-by: Petter <petter@mykolab.ch>

[...]

> +(define-public golang-github-com-sasha-s-go-deadlock
> +  (package
> +    (name "golang-github-com-sasha-s-go-deadlock")
> +    (version "341000892f3dd25f440e6231e8533eb3688ed7ec")
> +    (source (origin
> +              (method git-fetch)
> +              (uri (git-reference
> +                    (url "https://github.com/sasha-s/go-deadlock")
> +                    (commit version)))
> +              (file-name (string-append name "-" version "-checkout"))
> +              (sha256
> +               (base32
> +                "1bcdyxwm5qpqynxahwaahbqi7ghgdajmg7b4276pdalkxkxkhsv8"))))
> +    (build-system go-build-system)
> +    (arguments
> +     `(#:import-path "github.com/sasha-s/go-deadlock"))
> +    (propagated-inputs
> +     `(("golang-github-com-petermattis-goid" ,golang-github-com-petermattis-goid)))

There are a handful of packages, like this one, that seem to need their
dependencies propagated, or else building Syncthing fails when the
package fails to find its dependency.

This suggests to me that the Syncthing build process is not using the
compiled objects of these packages but is instead trying to rebuild
them.

So, perhaps something is not quite right with the go-build-system — I'm
not sure.