- From: Dirk Pranke <dpranke@chromium.org>
- Date: Mon, 22 Jul 2013 13:26:00 -0700
- To: Ms2ger <ms2ger@gmail.com>
- Cc: Martin J. Dürst <duerst@it.aoyama.ac.jp>, public-test-infra <public-test-infra@w3.org>
Received on Monday, 22 July 2013 20:26:49 UTC
On Mon, Jul 22, 2013 at 12:41 AM, Ms2ger <ms2ger@gmail.com> wrote: > On 07/22/2013 06:29 AM, "Martin J. Dürst" wrote: > >> On 2013/07/21 17:07, Tobie Langel wrote: >> >>> On Saturday, July 20, 2013 at 9:35 AM, "Martin J. Dürst" wrote: >>> >>> Existing code (.htaccess) has a dependency we don't want to have: >>> Apache. So either way we'll be writing code. >>> >> >> I got as far as understanding that some people don't want to depend on >> Apache. I haven't yet understood why. Pointer or explanation appreciated. >> > > Mozilla has the requirement that tests can be run locally by our > developers (volunteers as well as paid staff), and I think it's unlikely > that an Apache dependency will be considered acceptable. > > For the record, Chromium/Blink's testing infrastructure currently requires either Apache or Lighttpd. We're not necessarily overjoyed to depend on Apache, but it's not upsetting either (i.e., it's quite acceptable). WebKit's requires Apache. Both are fully capable of running the tests locally, and I'm a bit puzzled by why that would be difficult. (It is admittedly harder on Win32). That said, coming up with something lighter weight wouldn't be a bad thing. However, we have a lot of proprietary tests that also require Perl or PHP, and so even if the W3C tests switched to all using Python, we might still require Perl/PHP (and hence Apache/Lighttpd) for some indefinite period of time. -- Dirk
Received on Monday, 22 July 2013 20:26:49 UTC