version up: HAProxy 1.8.23, including security fixes.
-
Owner
@jerome Do you think we can add
CPU=native
inmake-options
as well, that will add-march=native
in CFLAGS ? (see https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html) -
Owner
It's a bit off topic, but everytime I see
"$(uname -m 2>/dev/null|grep -E '^(x86_64|i[3456]86)$')"
I wonder why we use https://www.buildout.org/en/latest/topics/variables-extending-and-substitutions.html#conditional-configuration-sections instead -
Owner
but yes ... why don't we use "native" looks also easier. I don't know this haproxy profile, but it looks very complex, probably we can simplify
-
Maintainer
let's ask @luke , he did something like this in a development branch
Adding haproxy 2 required this change luke/slapos@122f833a, in haproxy 2 the target became
linux-glibc
. -
Owner
If there is no strong reason, just update to haproxy 2 please. :)
-
Owner
FYI, I checked HAProxy 2 documentation and also checked our existing SR tests. Now I am sure we can safely use haproxy 2 everywhere. I will update soon.
-
Owner
-
Maintainer
Thanks, so I'll pick up it in my branch.