On Wed, Aug 30, 2006 at 12:23:55AM -0300, Avi Alkalay wrote: > Actually the daemon is designed to work with any backend. > 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.
The link points to the berkeley backend in the default case. > 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. spec file is not the place for marketing... It should be correct, simple, sound from a packaging perspective and work out of the box for most configurations. When there was no daemon it was sound to have a separate package since it adds some dependencies on db, and was optionnal. Now with the daemon having a separated package complicates the matter a lot, given that both must be installed at the same time anyway. What could make sense would be to ship the daemon in a separate package. But I think it is better in the main package. Do you want to have the dameon in a separate package? -- Pat ------------------------------------------------------------------------- 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
