Hi Georg,

Thank you for reaching out!

We’ve been discussing providing signed RPMs for more recent Linux versions and would love to have some further discussion on other distributions.

Currently the instructions for building the software probe are for RPM and DEB only, see here: https://github.com/RIPE-NCC/ripe-atlas-software-probe/blob/master/INSTALL.rst. However, we’re refactoring and will soon provide autoconf support for building the package. That should make packaging a lot easier. I expect it to be available with the next release.

The hardcoded lib event is something that came with the projects’ history. A partial support was added for (I believe) HTTP or SSL or a combination of both, but the implementation was not full so it was never sent upstream. My personal idea would be to first statically link in the lib event rather than as a .so file, that way the dependency is compile time only. Secondly, refactoring it out may or may not be feasible, that would have to be looked at.

Hope this helps!

Cheers,

Michel

On 18 Dec 2022, at 21:44, Georg <g.schlisio@dukun.de> wrote:

Hi,
I'd like to build the sofware probe from source for Archlinux, and would like to provide the resulting recipe (a so-called PKGBUILD) to the Arch User Repository as well.
Reading through the build scripts for debian and centos left a few open questions, is there any direction on how to build the sw probe without these scripts?
I'd like to avoid using the hardcoded libevent 2.1.11 or even a bundled busybox, is this possible and foreseen?
A pointer to build instructions would be much appreciated.

Thank you in advance
Georg

ps: after subscribing to this mailinglist I received a welcome message with a bunch of outdated links, you might want to consider updating them.


--
atlas-sw-probes mailing list
atlas-sw-probes@ripe.net
https://lists.ripe.net/mailman/listinfo/atlas-sw-probes