At 22:46 -0700 2001.04.12, Jim Popovitch wrote:
>Chris, The whole INSTALL.debian file suggests that one can install
>Debian packages rather than having to build things according to the
>INSTALL file. Is there a definitive agreement on whether or not this
I never use packages, I don't know. I was hoping someone else could say.
As I noted before, the only thing that I am aware of that you must build
from the source (unless your binary happens to have all the proper
configuration options compiled in) is Apache/mod_perl; no one has said
anything about the other packages possibly not working. Yes, I know that
the INSTALL.debian file says you can use libapache-mod-perl and apache
packages. Is this true? I do not know. I am perfectly willing to change
that, but I don't know.
>If not, why have that file in the distro? If pieces of the
>file are false, why leave them in the file? Maybe you are not the
>person who handles this. Is there someone else who puts the
I do much of putting the distribution together, and I do most of the
documentation. I cannot verify everything that goes into it. I never use
packages on Debian (or anywhere else, for that matter). As you can see,
INSTALL.debian was contributed by a third party. I am not aware of any
having specific complaints about its contents.
>As for the mod_perl differences, maybe you can't speak to their need.
>Is there possibly someone with more insight, who is deeply involved
>with Slash, that could possibly explain *why* these differences are
>needed. I.E. which specific part of Slash requires PERL_MARK_WHERE=1
EVERYTHING=1 enables all of the standard options. There are a lot of them,
and Slash depends on a lot of them. I don't know which ones the default
mod_perl installs for Red Hat and Debian don't have. If someone else could
tell us that, that'd be great. Again, I don't use packages, and don't
really know much about them.
I do know that Jon Pater mentioned once something about possibly getting
the Debian folks to build all of the needed options into their default
mod_perl, but I don't know what came of it, if anything.
>Having to recompile your webserver, just to run Slash, may have been
>cool with version 1.0. However this is the 2.0 release, can't *we* do
>what other weblogs/storyboards are capable of without recompiles of
>standard software components? Maybe that is nirvana. But if we aim
>for perfection we will only be that much closer.
Well, I understand how that is your idea of perfection/nirvana, but it
isn't mine. If we could identify the sections of the default binaries of
mod_perl that were not working, that could be helpful. But I don't know
what they are and have no real way of finding out.
Chris Nandor pudge@... http://pudge.net/
Open Source Development Network pudge@... http://osdn.com/