From: Gordon Pettey <petteyg359@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/1] 2025-02-21-NGINX-packaging-changes: Add news item
Date: Sun, 23 Feb 2025 14:22:38 -0600 [thread overview]
Message-ID: <CAHY5MedoJDOUgoosz0_fFNcq2Cg0FkHnnKYyOcePwy4aBO13Qg@mail.gmail.com> (raw)
In-Reply-To: <kgxvqrdywod3erjo676bsumgegny4t33r2h3jmicry24fejvzl@d6pexzyp3dx7>
On Sat, Feb 22, 2025 at 8:57 PM Zoltan Puskas <zoltan@sinustrom.info> wrote:
>
> Hi,
>
> This seems to be a significant change to nginx. While I think breaking out
> modules is a good idea, I was wondering how it was determined which modules are
> low usage or "needless"? I think some of these module removals actually might
> break other Gentoo packages in some cases.
>
> - nginx-dav-ext-module/http_dav_ext_module:
>
> This is required for anyone self hosting anything DAV. One such app in the
> Gentoo repository is www-apps/baikal, which if paired with DAVx5 [1] Android
> application, can be used as a self-hosted private contacts and calendar backend.
This removal will also break out-of-tree usage of e.g. Sonatype Nexus
(or any other
repository) hosting of Maven-based sites, as DAV is used to upload files.
next prev parent reply other threads:[~2025-02-23 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:36 [gentoo-dev] [PATCH 0/1] 2025-02-21-NGINX-packaging-changes: Add news item Zurab Kvachadze
2025-02-21 15:36 ` [gentoo-dev] [PATCH 1/1] " Zurab Kvachadze
2025-02-23 2:55 ` Zoltan Puskas
2025-02-23 20:22 ` Gordon Pettey [this message]
2025-02-24 22:23 ` [gentoo-dev] On retiring third-party NGINX modules (was: Re: 2025-02-21-NGINX-packaging-changes: Add news item) Zurab Kvachadze
2025-02-28 14:47 ` [gentoo-dev] [PATCH 1/1] 2025-02-21-NGINX-packaging-changes: Add news item Tomas Mozes
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=CAHY5MedoJDOUgoosz0_fFNcq2Cg0FkHnnKYyOcePwy4aBO13Qg@mail.gmail.com \
--to=petteyg359@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/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