[Lunar-commits] <moonbase> aliases: Adding lighttpd.

[Dennis Veatch]

On 02/25/2012 05:46 AM, Jean Bruenn wrote:
> Hello,
>
> The "problem" lies in between the recent rename of apache2 to
> httpd which is not a good thing. Even if the Apache folks name their
> repository and project "httpd" the module name should be "apache2" as
> it's "apache2" httpd stands for a HTTP-Daemon - Apache2 is one, Apache1
> is one, Lighttpd is one, should I continue? If you rename apache2 to
> httpd then please rename firefox to browser and sylpheed to
> mail-client. A new user, trying to install apache2 will always look for
> "apache2" and _not_ for httpd.
>
> Keeping that in mind, the proper solution would be to have an alias
> called "httpd" or even "webserver" which has apache2, lighttpd,
> apache1, apache-ssl if you really care.
>
>> What you've done is promoted lighthttpd to be equivalent to apache,
>> apache2. But nothing in your commit says that you've tested
>> everything that requires %APACHE to work with lighthttpd.
>>
>> $ grep -rl %APACHE *
>> compilers/aubit4glsrc/DEPENDS
>> web/bitweaver/DEPENDS
>> web/drupal/DEPENDS
>> web/htdig/DEPENDS
>> web/mod_scgi/DEPENDS
>>
>> So, did you test these packages to work with lighthttpd as "%APACHE" ?

No I did not test them. I did research to see if there were 
compatibility issues in the vein of them absolutely not working with 
lighttpd and there are none that I know of; the mod_scgi I am not sure 
about.

Additionally, none of those are one hundred percent integrated with 
Apache in the sense of install it and your good to go. The user still 
needs to fiddle about with Apache confs or the respective confs of those 
modules and they will need to do the same if lighttpd is chosen. In that 
respect it is no different.

If that is still bothersome I have no problem reverting my commit. Just 
say the word.


> I haven't checked them yet, I'll do together with dveatch if he has
> time/wants. However, from what I can tell now: netiher drupal nor htdig
> are integrated parts or dependencies or need specific things of apache
> to work; they'll work fine in lighttpd too. Furthermore drupal is a
> content management system - That one should work in nearly every
> webserver, just like php5, phpmyadmin, etc.
>
> So what should we do now? alias with name HTTPD containing all
> webservers? Revert florin's rename of apache2 to httpd? Going to the
> bar drinking a few beers?
>
> Jean
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-dev
>


-- 
Dennis `stumbles` Veatch
Lunar Linux Developer
http://www.lunar-linux.org/