It makes more sense currently to use it with BDB, and not with filesys. But in general, the daemon is not related to any backend.
I have no solid opinion about BDB package separation or unification.
I think it currently works as a "marketing" thing that shows (a) we have other backends, (b) we have a berkeleydb backend and that (c) backends are modular and independent from the main lib.
Regards,
Avi
On 8/24/06, Patrice Dumas <[EMAIL PROTECTED]> wrote:
On Wed, Aug 23, 2006 at 11:24:27PM -0300, Avi Alkalay wrote:
> I was far for a while, now I'm back.
>
> I saw many changes in the repo. Thats great !
> How much of this report is fixed already ?
>
> I cleanly built an RPM. And the build system seems nicer.
>
> How far are we from a 0.6.4 release ?
Not far.
Regarding the rpm, I think that it doesn't make sense to ship a
separate backend-berkeleydb from the main package now that the daemon
backend requires it in the default case. Agreed?
--
Pat
--
my blog: http://avi.alkalay.net/
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Registry-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/registry-list
