You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It transitively pulls in etcd, prometheus, protobuf and grpc. I believe this is all because of the warthog618/config library used in the commandline tools.
My poor little Raspberry Pi Zero W gets overwhelmed just trying to download everything.
Would you be open to a PR that converts to plain Go flag handling and removes that dependency?
The text was updated successfully, but these errors were encountered:
The use of config is more pervasive than you think - it is in the examples as well and also uses config files not just flags.
I have a couple of patches locally where I looked at switching to spf13/pflag and spf13/viper, as those are commonly used for configuration, but that makes the dependency situation worse:
go mod graph | wc -l
2371
I also considered using the standard Go flags for the tools, but the intent was to emulate the libgpiod command line and output as closely as possible and if I recall correctly that wasn't possible with the Go flags.
I recommend cross-compiling for your Pi Zero on a different platform - that is what I do.
Yeah, I started cross-compiling. Definitely much better.
fwiw, I've started migrating to alecthomas/kong. I really like it, and it's quite lightweight. And if you want config files, there's kong-hcl or kong-yaml.
It transitively pulls in
etcd
,prometheus
,protobuf
andgrpc
. I believe this is all because of thewarthog618/config
library used in the commandline tools.My poor little Raspberry Pi Zero W gets overwhelmed just trying to download everything.
Would you be open to a PR that converts to plain Go flag handling and removes that dependency?
The text was updated successfully, but these errors were encountered: