public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] New: httpd-2.4.12-1 (obsoletes: apache2)
Date: Fri, 22 May 2015 20:21:00 -0000	[thread overview]
Message-ID: <announce.1432325976.8768.29.camel@cygwin.com> (raw)

The following packages have been added to the Cygwin distribution:

* httpd-2.4.12-1
* httpd-devel-2.4.12-1
* httpd-manual-2.4.12-1
* httpd-tools-2.4.12-1
* httpd-mod_ldap-2.4.12-1
* httpd-mod_lua-2.4.12-1
* httpd-mod_proxy_html-2.4.12-1
* httpd-mod_ssl-2.4.12-1

The Apache HTTP Server Project is a collaborative software development
effort aimed at creating a robust, commercial-grade, featureful, and
freely-available source code implementation of an HTTP (Web) server.

This is the latest upstream version, intended to replace the 2.2 version
provided by the 'apache2' packages.  But first, some history:

httpd 1.x was originally packaged for Cygwin as 'apache', possibly
matching the Debian package name, while still keeping the upstream
'httpd' file names.  When 2.0 came out, it was decided to create a
separate package which did not collide with 1.3 to aid the transition,
where all binary and directory names were versioned with '2', and hence
the package was named 'apache2'.

Unfortunately the incomplete and inconsistent renaming of 'apache2'
required a hackish patch which I then inherited some time ago and could
not drop without breaking compatibility during the 2.2 series.  Because
of the API and configuration changes involved in upgrading from 2.2 to
2.4, the opportunity was taken to avoid these renaming hacks and make
other changes to the packaging layout.

Therefore, installing 'httpd' will currently neither remove nor clobber
the 'apache2' packages.  This is being done to allow time for users to
reconfigure (which has to be done anyway) and rebuild any third-party
DSOs.  Please note that the 'apache2' packages will not be supported any
further, and in the near future, httpd will fully obsolete (and
uninstall) the apache2 packages.

The packaging changes are extensive in this release:

* All binaries use their original upstream names.

* The configuration files are now in /etc/httpd/conf, and all modules
and conf files can be referenced as relative paths to /etc/httpd.

* cyghttpd2core.dll (which required another hack) has been replaced by
exporting symbols from httpd.exe itself, which can be linked to with
-lhttpd.

* Modules which provide APIs which other DSOs require at link time have
been built statically into httpd, namely: mod_cache, mod_dav, mod_proxy,
mod_session, and mod_unixd.

* Modules with non-core dependencies are packaged separately.

* apxs is part of the -devel package again.  Instead of using apxs to
(un)install modules during postinstall/preremove, LoadModule config
snippets should be used instead.

* A new httpd.cygclass has been added to cygport git, which should be
used in place of apache2.cygclass.

--
Yaakov

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

                 reply	other threads:[~2015-05-22 20:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=announce.1432325976.8768.29.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).