FS#33586 - [nginx] Custom configurations should be in separate packages

Attached to Project: Community Packages
Opened by Alain Kalker (ackalker) - Saturday, 26 January 2013, 21:24 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Wednesday, 30 January 2013, 09:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Sadly, nginx doesn't support adding loadable modules after it has been compiled. This means that each customization requires recompiling nginx.

In keeping with Arch Linux tradition of providing packages which are as close as possible to the intentions and default configuration of upstream, separating out customization into separate packages (sometimes from the AUR), I think that the 'nginx' package also should stick as closely as possible to the functionality provided by upstream.

Therefore, I would like to suggest putting customizations of nginx into separate packages, each providing 'nginx'.
This mitigates the risk of unforeseen {performance,security,functionality} effects (see for example  FS#33582 ), while still leaving users choice.

There are many examples of such nginx customizations already available in the AUR.

Regards, Alain
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Wednesday, 30 January 2013, 09:02 GMT
Reason for closing:  Won't fix

Loading...