thanks to https://www.freshports.org/www/mod_md-devel/ i learned that mod_md-devel
DEPRECATED: Use the module that is shipped with Apache 2.4
Expired This port expired on: 2019-03-24
and was as such, removed from latest.
However, the apache24 package provided in latest, does *not* come with a mod_md module.
the most recent apache24 port has the MD option. Select this option and everything should be fine.
I understand the consequence, and what i need to do, i just don't agree.
Closing the port, means that a *binary* package is gone.
From the closing message, it ~feels~ like you could just get away with installing a different binary package. But that is just a lie i wanted to believe.
downloading the ports tree, and rebuilding a package, is *vastly* different UX compared to … installing a package. Especially on my very cheap cloud VM.
Hmm, mod_md is part of apache since at least July 2018, I guess. I even think (might be wrong) that it's also part of the default build, so the generic
freebsd repo should have the package with mod_md -- is that not the case ?
root@webproxy:~ # freebsd-version
root@webproxy:~ # pkg info apache24
Name : apache24
Version : 2.4.39
Installed on : Fri May 3 10:50:59 2019 UTC
Origin : www/apache24
Architecture : FreeBSD:12:amd64
Prefix : /usr/local
MD : off
also, according to http://svn.freebsd.org/ports/head/www/apache24/Makefile.options
AUTHNZ_LDAP BROTLI IDENT LDAP LUA MD SOCACHE_DC SOCACHE_REDIS SUEXEC
Ok, I agree, this should be default in the generic repo
*** Bug 237727 has been marked as a duplicate of this bug. ***
Created attachment 204198 [details]
Add MD to MOST modules