<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] lighttpd and others now require apache
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20lighttpd%20and%20others%20now%20require%20apache&In-Reply-To=%3C4F6AE7D3.5010903%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013345.html">
<LINK REL="Next" HREF="013405.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] lighttpd and others now require apache</H1>
<B>Guillaume Rousse</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20lighttpd%20and%20others%20now%20require%20apache&In-Reply-To=%3C4F6AE7D3.5010903%40gmail.com%3E"
TITLE="[Mageia-dev] lighttpd and others now require apache">guillomovitch at gmail.com
</A><BR>
<I>Thu Mar 22 09:50:27 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013345.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013405.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13358">[ date ]</a>
<a href="thread.html#13358">[ thread ]</a>
<a href="subject.html#13358">[ subject ]</a>
<a href="author.html#13358">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 22/03/2012 02:51, David Walser a écrit :
><i> Guillaume Rousse wrote:
</I>>><i> Le 17/03/2012 03:22, Anssi Hannula a écrit :
</I>>>><i> Hence I suggest a single user id to be used. (I'm fine with any other
</I>>>><i> solution which works as well)
</I>>><i> My main concern is the fuzziness of the current situation where we have
</I>>><i> - one virtual package 'webserver' corresponding to four implementations
</I>>><i> (apache, lightpd, nginx, cherooke)
</I>>><i> - one common base (webserver-base) only used by the two first ones
</I>>><i> - all our web applications packages using 'apache' as mandatory dependency
</I>>><i>
</I>>><i> If the main concern is file ownership, I'd propose for the next release
</I>>><i> to have each of these servers use a distinct uid, document root and
</I>>><i> index page, but use a shared 'webserver' or 'www' gid, and ensure all of
</I>>><i> those applications use group-based permission, instead of user-based.
</I>>><i> I'd find this setup a bit clearer.
</I>><i>
</I>><i> I also noticed two of the php subpackages adding the apache user in %post.
</I>><i> Should they be doing this, should they Requires(post): webserver-base, or
</I>><i> should this be handled some other way?
</I>Sure, that's wrong.
Either they need apache itself, in this case this dependency is already
ensured. Either they can be used without a web server, in this case they
shouldn't use apache server anyway.
--
BOFH excuse #161:
monitor VLF leakage
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013345.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013405.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13358">[ date ]</a>
<a href="thread.html#13358">[ thread ]</a>
<a href="subject.html#13358">[ subject ]</a>
<a href="author.html#13358">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>