update apache2 in lucid or backport some features?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Lucid Backports |
Won't Fix
|
Undecided
|
Unassigned | ||
apache2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apache2
Hi,
the newer apache2 packages (e.g. 2.2.16 in Maverick) contain some important functionality that is currently missing in Lucid: support for running multiple instances of apache in the same host.
This is a great admin help wrt configuring and running web servers, as it allows painless set up of different apache instances configured to run different sets of modules, on different ports, and/or running under different user IDs.
See for example:
http://
http://
http://
And given that many web servers are running on LTS releases, it makes perfect sense for lucid to have this functionality.
FreeBSD has had a similar functionality since ~ 2006 ...
I know there are some issues with libssl versions that prevent bringing more recent versions of apache2 into lucid ... but maybe this particular functionality can be backported?
The relevant changes in the package are summarized here:
http://
http://
But it may be a good idea to check with Stefan Fritsch (sf at alioth.debian.org, https:/
Cheers,
--
fernan
Changed in lucid-backports: | |
status: | New → Won't Fix |
Hi Fernan, this is an excellent idea, thanks for taking the time to file the report and help us make Ubuntu better.
There is a fairly well documented procedure for requesting backports to lucid, defined here:
https:/ /help.ubuntu. com/community/ UbuntuBackports #How to request new packages
Apache is recommended by quite a few packages, and probably depended on by a lot, so I don't know if it is entirely acceptable for backports. However, I'd support the effort if some core devs and / or MOTU's feel that its worth doing.
Changing bug report to affect lucid-backports, marking Confirmed / Wishlist.