Re: Apache situation.
On Fri, Jan 28, 2000 at 08:12:35AM -0700, C. R. Oldham wrote:
> Enter apache-perl. Whoops, apache-perl is missing most of the
> good stuff that comes with the regular apache package. Oh yeah, and
> Apache::DBI depends on libapache-mod-perl. Oops, lots of Apache modules
> depend on apache, not apache-perl. Argh!
huh?
two days ago, i ran "apt-get install apache-perl". it replaced apache
and libapache-mod-perl. there were no problems at all, no unresolved
dependancies, no conflicts. it just worked (and with greatly reduced
memory consumption over apache + libapache-mod-perl...6MB apache
processes rather than 20MB)
the apache-perl package has the following lines in its control file:
Replaces: apache-modules, apache, libapache-mod-perl
Conflicts: apache-modules, apache, libapache-mod-perl
Provides: httpd, apache, libapache-mod-perl
these ensure that it replaces those packages, and that all dependancies
are met.
e.g. Apache::DBI (libapache-dbi-perl) depends on libapache-mod-perl.
apache-perl provides that package, so there is no dependancy problem.
> So I've spent the better part of two days rebuilding the apache
> package to support mod_perl statically linked. I just about have
> it, the last stumbling block is that I can't figure out how to get
> the mod_perl perl-side stuff into the package because the mod_perl
> installer thinks I
if you ever need to compile your own version of any debian package,
the best thing to do is to download the debianised sources, make
whatever changes you need, and then build your own package (i.e. run
"dpkg-buildpackage" rather than "./configure ; make ; make install").
your package can be installed, upgraded, removed etc with dpkg just like
any other package.
> After I get this done I either have to modify the libapache-dbi-perl
> package to ignore the dependency on libapache-mod-perl, or strip the
> mod-perl package to contain nothing just so I can have the dependency
> satisfied. Or I could use dpkg --force, but that makes apt complain
> a lot, and requires that all the people that help me maintain the
> servers know exactly what's going on.
no, you don't need to do that at all. the apache-perl package Provides
all the needed dependancies.
> Also, none of this takes into account the fact that someone is
> probably going to want to run Apache both with and without mod_perl to
> lower memory consumption. I have no idea how to handle that since the
> binaries would have to be called apache and apache-mod-perl, and look
> for their conffiles in separate places, or whathaveyou. Currently
> I don't know if the project ever solved the problem of multiple
> webservers running simultaneously.
look at how this was done for the apache-ssl package. it co-exists quite
happily with normal apache (although libapache-mod-ssl is a better SSL
solution IMO).
craig
--
craig sanders
Reply to: