On Thu, Mar 15, 2001 at 09:27:09PM -0600, William A. Rowe, Jr. wrote:
> While we are doing this 'right'...
>
>
> package dbmmanage;
> # -ldb -lndbm -lgdbm -lsdbm
> BEGIN { @AnyDBM_File::ISA = qw(DB_File NDBM_File GDBM_File SDBM_File) }
> use strict;
> use Fcntl;
> use AnyDBM_File ();
>
>
> Really, let's get this right. It isn't anyfile in order that they are built
> into the Perl distro! This is whatever was built into either mod_auth_dbm or
> mod_auth_db. Can we get the subst var for the right dbm package? And if
> they build auth_db, perhaps we write this file as dbmanage , so the user will
> conceivably have both if they build both auth_db and auth_dbm?
>
> This is tricky if they use apu_dbm. We are 'using' apr-util, so we need to
> learn what apr-util used. But we have enough make hackers to get this right
> finally, after a few years (see bugs. for several reports :-)
First step is to toss mod_auth_db and just use mod_auth_dbm against apr_dbm.
I don't have the best setup for testing this, but am happy to Just Do It and
rely on testing from others.
Oh, actually, it is "merge" mod_auth_db into mod_auth_dbm. IIRC, the two
don't look quite the same, and mod_auth_db has some extended error checks.
We'd need to ensure the error checks are available all the way thru the
apr_dbm interface. Then, we merge the two modules.
Second step is to add ndbm capability to apr_dbm. That would allow
mod_auth_dbm to just use apr_dbm, rather than have separate config stuff for
ndbm.
Once we have just mod_auth_dbm working against apr_dbm, then we can tweak
dbmmanage to use whatever APRUTIL chose for the apr_dbm interface. That
won't be a problem. It is the steps above which takes some coding/testing.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
