This arguement has been going on the HTTPD-dev list recently too.
Defining some terms should answer your question.

Binaries are provided by volunteers who have commit access to the HTTPD
project. They are not formally provided by the Apache Software Foundation.

There is ongoing discussion on the dev list about a way forward with regard
to Windows binary distribution. In the mean time, try the ApacheLounge
binaries. (if I was not using a mobile device, I would post a link, but it
should be easy enough to find anyway.)

That said, please do not email the dev list to complain about the lack of
"official" binaries. If you have any experience in automating the build
process on Windows, that might be appreciated.

- Y

On Sunday, December 16, 2012, Esmond Pitt wrote:

> I know this has been discussed before but is this a policy change? I've
> been
> downloading Apache 2 Windows binaries direct from the project for about ten
> years.
>
> EJP
>
> -----Original Message-----
> From: Tom Evans [mailto:tevans...@googlemail.com <javascript:;>]
> Sent: Thursday, 13 December 2012 11:31 PM
> To: users@httpd.apache.org <javascript:;>
> Subject: Re: [users@httpd] Apache HTTP Server 2.4.x for Windows?
>
> On Tue, Dec 11, 2012 at 4:47 PM, Ben Johnson 
> <b...@indietorrent.org<javascript:;>>
> wrote:
> > The Apache Software Foundation does not provide Windows binaries. You
> > must compile the software from source (no simple matter on Windows) or
> > obtain binaries from a third party. Apache Lounge is the best known
> > source for such binaries: https://www.apachelounge.com/download/
>
> Just to clarify, this is not specific to Windows. The Apache httpd project
> doesn't provide any binaries for any platform.
>
> Cheers
>
> Tom
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org <javascript:;>
> For additional commands, e-mail: users-h...@httpd.apache.org<javascript:;>
>
>

-- 
Sent from a gizmo with a very small keyboard and hyper-active auto-correct.

Reply via email to