Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>, Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH 1/2] package/apache: add config option to enable mod_md
Date: Tue, 30 Dec 2025 14:19:16 +0100	[thread overview]
Message-ID: <20251230141916.67724e91@windsurf> (raw)
In-Reply-To: <20251207214849.757334-1-fiona.klute@gmx.de>

On Sun,  7 Dec 2025 22:48:47 +0100
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:

> mod_md allows Apache httpd to automatically provision certificates for
> HTTPS via the ACME protocol (e.g. from Let's Encrypt), if configured
> to do so. The additional dependencies are non-obvious, so add a config
> option instead of only enabling the module if dependencies are met.
> 
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
> ---
>  package/apache/Config.in | 12 ++++++++++++
>  package/apache/apache.mk |  9 +++++++++
>  2 files changed, 21 insertions(+)

Thanks, both patches applied!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2025-12-30 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07 21:48 [Buildroot] [PATCH 1/2] package/apache: add config option to enable mod_md Fiona Klute via buildroot
2025-12-07 21:48 ` [Buildroot] [PATCH 2/2] package/apache: fix checkpackage warnings in init script Fiona Klute via buildroot
2026-01-13 19:46   ` Arnout Vandecappelle via buildroot
2025-12-30 13:19 ` Thomas Petazzoni via buildroot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251230141916.67724e91@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=fiona.klute@gmx.de \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox