From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Jim Reinhart <jimr@tekvox.com>, James Autry <jautry@tekvox.com>,
Giulio Benetti <giulio.benetti+tekvox@benettiengineering.com>,
Matthew Maron <matthewm@tekvox.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/apache-utils: new package
Date: Thu, 14 Sep 2023 21:49:42 +0200 [thread overview]
Message-ID: <20230914214942.41dd792a@windsurf> (raw)
In-Reply-To: <20230914191726.28670-1-giulio.benetti@benettiengineering.com>
Hello Giulio,
On Thu, 14 Sep 2023 21:17:26 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> From: Giulio Benetti <giulio.benetti+tekvox@benettiengineering.com>
>
> Build htdigest and htpasswd utilities only without building entire Apache
> package.
>
> Cc: Jim Reinhart <jimr@tekvox.com>
> Cc: James Autry <jautry@tekvox.com>
> Cc: Matthew Maron <matthewm@tekvox.com>
> Signed-off-by: Giulio Benetti <giulio.benetti+tekvox@benettiengineering.com>
Thanks for the proposal. I'm always a bit "meh" when it comes to adding
a new package that uses the same source code as another package. It
causes extra maintenance work (you need to update both packages, apply
patches to both, keep tracking of CVEs for both, etc.).
What is the use case for needing this without the Apache server? Can we
change the Apache package to instead allow installing only those tools?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-14 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 19:17 [Buildroot] [PATCH] package/apache-utils: new package Giulio Benetti
2023-09-14 19:49 ` Thomas Petazzoni via buildroot [this message]
2023-09-14 20:11 ` Giulio Benetti
2023-09-15 22:17 ` Yann E. MORIN
2023-09-17 20:26 ` Giulio Benetti
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=20230914214942.41dd792a@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti+tekvox@benettiengineering.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=jautry@tekvox.com \
--cc=jimr@tekvox.com \
--cc=matthewm@tekvox.com \
--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