Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

> > will this have any pitfalls? is there anything i'm not aware of? > > For the paranoid, from man ldd, red emphasis mine (if it worked) i included ldd's output only for reference. what i meant to ask is this: is it a dirty hack to run a (trusted) binary file like this: $

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

On +2021-09-03 08:16:00 +, Attila Lendvai wrote: > > [with some reorderings] > > > I hope my reply has been valueable. It seems like this discussion > > is going to end with ‘agreeing to disagree’ and I think I said all > > I've got to say about the philosophical part of the matter, so I > >

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

[with some reorderings] > I hope my reply has been valueable. It seems like this discussion > is going to end with ‘agreeing to disagree’ and I think I said all > I've got to say about the philosophical part of the matter, so I > don't think I'll sending further replies on the philosophical

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

Hi, Maxime Devos writes: >> > have uses outside go-ethereum, so they can be re-used as dependencies of >> > new go packages, so over time, having to define many new packages when >> > importing >> > a go application should become less and less of a problem. >> > >> > (About version pinning:

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

Attila Lendvai schreef op wo 01-09-2021 om 14:29 [+]: > On Wednesday, September 1st, 2021 at 00:21, Maxime Devos > wrote: > > > Hi, > > > > Warning: I haven't actually ever touched a go package. Take my mail > > with a huge grain of salt. > > Much of this you've probably already heard at >

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

On Wednesday, September 1st, 2021 at 00:21, Maxime Devos wrote: > Hi, > > Warning: I haven't actually ever touched a go package. Take my mail > with a huge grain of salt. > Much of this you've probably already heard at > https://logs.guix.gnu.org/guix/2021-08-31.log#024401. > > Attila Lendvai

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

Hi, Warning: I haven't actually ever touched a go package. Take my mail with a huge grain of salt. Much of this you've probably already heard at . Attila Lendvai schreef op ma 30-08-2021 om 21:52 [+]: > [...] > so, regarding

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

FTR, we had a discussion about this on IRC: https://logs.guix.gnu.org/guix/2021-08-31.log#024401 conclusion: ideally, Guix should have a pinned package for each go dependency, and with the go importer it's not hopeless to do anymore. it conflicts with the general Guix policy to package the

packaging go-ethereum, and ultimately bee (of ethswarm.org)

hello everyone, it's my first mail here, so let me briefly into myself: i'm a long-time lisper (mostly CL, i'm new to Scheme, although i worked on a scheme-like tiny lisp: https://github.com/attila-lendvai/maru). i'm coming over from NixOS after a few months of loving it as a user, but hating