On Sat, Dec 15, 2018 at 07:19:49PM +0100, Pierre Neidhardt wrote:
>
> > So hmm, you’re right! I’m sure I saw go packages somewhere, dunno…
>
> Just looked at the source: after my Go 1.11 update, Syncthing was updated to
> use
> vendored dependencies, just like go-ipfs. This is why it does not
On Sat, Dec 15, 2018 at 07:19:49PM +0100, Pierre Neidhardt wrote:
>
> > So hmm, you’re right! I’m sure I saw go packages somewhere, dunno…
>
> Just looked at the source: after my Go 1.11 update, Syncthing was updated to
> use
> vendored dependencies, just like go-ipfs. This is why it does not
Hello,
Pierre Neidhardt skribis:
>> Oh, we should really work towards unbundling things from ‘go-ipfs’. Any
>> idea how difficult that would be?
>
> go-ipfs has more than 100 deps. So unless we work on a recursive importer,
> it's
> going to be a lot of work.
>
> Harder: those dependencies ca
> So hmm, you’re right! I’m sure I saw go packages somewhere, dunno…
Just looked at the source: after my Go 1.11 update, Syncthing was updated to use
vendored dependencies, just like go-ipfs. This is why it does not contains any
go ref. From the package declaration:
;; Since the
Pierre Neidhardt skribis:
> go-ipfs is fine indeed, but that's because you've just looked at the lucky
> package! go-ipfs vendors all the Go dependencies, which is why there is no
> extra input there and go-ipfs closure size is optimal.
Oh, we should really work towards unbundling things from ‘
Hello!
Pierre Neidhardt skribis:
> I've investigated the possible solutions to avoid including the paths into the
> binaries.
>
> I've found this:
>
> https://github.com/golang/go/issues/16860
>
> It's still unresolved and only planned for Go 1.13.
>
> In the meantime, I've played with the -trim
I've investigated the possible solutions to avoid including the paths into the
binaries.
I've found this:
https://github.com/golang/go/issues/16860
It's still unresolved and only planned for Go 1.13.
In the meantime, I've played with the -trimpath option to see if I could get
something out of i
On Mon, Nov 12, 2018 at 06:38:53PM +0100, Pierre Neidhardt wrote:
> Yes, it should be statically linked. Isn't it the same issue as we recently
> had
> with go-1.11 itself?
>
> The fix was
>
> --8<---cut here---start->8---
>;; Prevent installation
On Mon, Nov 12, 2018 at 06:38:53PM +0100, Pierre Neidhardt wrote:
> Yes, it should be statically linked. Isn't it the same issue as we recently
> had
> with go-1.11 itself?
>
> The fix was
>
> --8<---cut here---start->8---
>;; Prevent installation
On Mon, Nov 12, 2018 at 12:48:20PM -0500, Leo Famulari wrote:
> way, then it's time to finally move the Boyer-Moore implementation in
> (guix grafts) to its own module so we can use it easily.
Mistake — it's in (guix build grafts).
signature.asc
Description: PGP signature
On Mon, Nov 12, 2018 at 04:32:46AM -0500, Pierre Neidhardt wrote:
> commit 9a65a052016572b61e3c4247fcdf9e0478656f71
> Author: Pierre Neidhardt
> Date: Sun Nov 11 22:02:18 2018 +0100
>
> gnu: go: Update default to 1.11.
>
> * gnu/packages/golang.scm (go): Update default to 1.11.
I
11 matches
Mail list logo
