Guys, I think someone needs to point out the no_bindings and no_ap2 flavors.
With that most problems are solved, I suspect ;-) -- Todd Fries .. [EMAIL PROTECTED] _____________________________________________ | \ 1.636.410.0632 (voice) | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice) | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX) | "..in support of free software solutions." \ 250797 (FWD) | \ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A http://todd.fries.net/pgp.txt Penned by Steven Mestdagh on 20080902 23:25.49, we have: | Stuart Henderson [2008-09-02, 12:20:00]: | > On 2008/09/02 12:56, Stefan Sperling wrote: | > > Yes, keep SASL. svnserve needs it. | > | > If it would reduce the list of dependencies for the client, I'd be very | > keen to have the client and server split into separate multi-packages. | | Looks like both client and server get linked against libsasl2. | | > Having to install apache2 and SASL is slightly annoying if all you're | > trying to do is pull source from some project that doesn't bother to | > release proper tarballs :-) | | Huh? You don't have to install apache2. | | I see no reason to split it.
