Compiling instructions for building from source
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.
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.rs.... 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
Hi Michel, thank you for the reply. Thanks for pointing me to the install documentation. The prospect of the next release being buildable solely by automake sounds very good. Is there a (rough) time planning on this or is this the usual its-done-when-its-done? Statically linking a custom libevent is not a showstopper for sure, so this looks like a good way forward. Best Georg Am 21.12.22 um 13:30 schrieb Michel Stam:
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.rs.... 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
On 12/21/22 15:30, Michel Stam wrote:
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.rs... <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.
To add these to Fedora and CentOS repos, dynamically linked unbundled libraries are preferred. Libevent is available: https://packages.fedoraproject.org/pkgs/libevent/libevent There seems to be http and ssl support: https://github.com/libevent/libevent Libbb and Libpwdgrp are not, but busybox is available, so it would be possible to build shared libbb and libpwdgrp: https://src.fedoraproject.org/rpms/busybox Would there be interest in trying to support the standard versions of these libraries as well?
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
Hi Michel (and the sw-probe dev team), end of last year you mentioned an ongoing refactoring and coming autoconf support: 21.12.2022 13:30: Michel Stam:
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.
Whats the status of this? Not trying to push or anything, just making sure I didn't miss something here. Also indicating continued interest :) Best Georg
Hi Georg, The autoconf development is still ongoing, but has seen significant delays, because of staffing. The current status is that I have a development tree that is able to build RPM, Debian DEB and will build OpenWRT IPKG (both for hardware probes and as a feed to include in your build). The development tree has seen a lot of refactoring to conform to the Linux FHS, and I’m working with 2 people with the intent of having the software probe available from EPEL and contrib (sorry the official name Debian has for this escaped me for the moment). The intent here is taking the effort of releasing software away from the developers as well as making the installation process easier for users. Privilege separation will be implemented using 2 users, one handling the communication and the starting / stopping of processes, the other handling the actual execution of measurements. Sudo is being removed as it clutters the logfiles. The package will be released as a ripe-atlas-common (common functionality for all probe types), ripe-atlas-probe and ripe-atlas-anchor. The last one will only be installed on the request of RIPE NCC as this involves setting up an anchor. This is still under discussion, but is my current view on this. Because of this restructure the software will need testing and review, which takes a lot of time. I hope you understand. Dockers or others are something that can be looked at later, at the moment I’m trying to aim for feature parity and lots of testing before releasing this into the wild. Cheers, Michel
On 28 Sep 2023, at 10:19, Georg <g.schlisio@dukun.de> wrote:
Hi Michel (and the sw-probe dev team),
end of last year you mentioned an ongoing refactoring and coming autoconf support:
21.12.2022 13:30: Michel Stam:
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.
Whats the status of this? Not trying to push or anything, just making sure I didn't miss something here. Also indicating continued interest :)
Best Georg
participants (3)
-
Benson Muite -
Georg -
Michel Stam