Unless we have confirmed that these 'flavors' don't rely on non-dynamic modules that need compiled in at compile time I generally am in agreement. There were options enabled at some flavors that are not invseparately packaged modules because they needed to be in the executable at compile time.
Which means we need to validate that all modules still in the flavors are actually compiled into plain nginx. We also need to make sure the path of upgrade works still too. (nginx-extras to just nginx and stuff) Sent from my Galaxy -------- Original message -------- From: Jérémy Lal <kapo...@melix.org> Date: 12/8/22 13:33 (GMT-05:00) To: Debian Bug Tracking System <sub...@bugs.debian.org> Subject: [Pkg-nginx-maintainers] Bug#1025763: nginx: do nginx-extras nginx-full nginx-core nginx-light still make sense ? Source: nginx Version: 1.22.1-3 Severity: wishlist With all modules being built in their own separate packages, it would be less confusing to have just a "nginx" package, and let users install the modules they need. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled _______________________________________________ Pkg-nginx-maintainers mailing list pkg-nginx-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nginx-maintainers
