|
From: Roger L. <ro...@at...> - 2018-12-20 22:27:12
|
Dear all, I have packaged valgrind as a snap. In case you aren't familiar with snaps, they are containerised packages that bundle dependencies, and run on a variety of Linux distributions, but are most well supported on Ubuntu. The advantage for me is that they can provide up to date versions of software even on older distributions - so with this package, 3.14.0 is available on all supported versions of Ubuntu back to 14.04, for example. To install on a snap supported distro, you would run snap install --beta --classic valgrind At the moment the package is still very new so I have only released it to the beta channel. As far as I have used the different tools everything seems fine, but I had been hoping for some other feedback. Once it is fully released you would run snap install --classic valgrind In both cases you would then use the valgrind command line programs as normal, but they would be running from /snap/... instead. The store page for the package is https://snapcraft.io/valgrind I'm writing to tell you out of interest, but also in case you would like to take over providing this package. I think that binaries managed by upstream are best, where possible. I am very well aware that packaging is a thankless task, but in my experience of building debs, a bit of rpm, and homebrew, the update procedure for this is very straightforward. Just update the version number in the snap packaging file (https://github.com/ralight/valgrind-snap/blob/master/snap/snapcraft.yaml ), commit and push, then wait for the package to be autobuilt for all architectures and release it to the stable channel on the store. Having said all that, I'd be quite happy to keep on maintaining the package myself. Regards, Roger |