On 18.11.2011 19:15, Mark A. Hershberger wrote:
Dmitriy Sintsov<questpc(a)rambler.ru> writes:
Thanks, but I didn't just want to build the
same version of PHP from
source.
Sure, so my overview will just get you started.
The patches that Debian installs are listed in the debian/patches
directory. If you want to keep a patch out, you would remove it from
debian/patches/series.
For example, the patch to remove the configure options is
debian/patches/052-phpinfo_no_configure.patch, so to keep the configure
options, you would remove the "052-phpinfo_no_configure.patch" line from
debian/patches/series and re-run debuild.
To add patches, you should read up on quilt. I suggest this howto:
http://pkg-perl.alioth.debian.org/howto/quilt.html Thanks, your advices are really
valuable.
Also, they have very weird default setup for
apache vhosts: instead of
placing them into one includable httpd-vhosts.conf, they make lots of
small separate files one for each vhost and include the whole dir with *
wildcard. That might have unpredictable results, because in such way
it's hard to control the sequence of vhosts inclusion, and the order of
vhosts is important.
Why would your virtual hosts be load order dependent? Things
that
should be loaded before any virtual hosts should go into files in
/etc/apache/conf.d.
If you really don't like the use of /etc/apache2/sites-enabled and
/etc/apache/conf.d, then, of course you can use anything you like.
You'll have more work when you upgrade apache, but how much of the
upgrade work you want to outsource to Debian is your choice.
Virtual hosts are order dependent because I have the following
VirtualHost match:
ServerAlias *.domain
for many sites (wikifarm)
but for some selected sites I need to have another VirtualHost:
ServerAlias host1.domain
ServerAlias host2.domain
before "global" *.domain will match.
Dmitriy