kdbprivate.h must be shiped for production in a -devel package. It is needed for custom backend development, for example.

The /etc/kdb and ~/.kdb dirs in this file are from the time Elektra didn't have pluggable backends. It is a backend responsability to define this directories. In the future (near near future), maybe these dirs should dispear from kdbprivate.h

Regards,
Avi

On 8/14/06, Patrice Dumas <[EMAIL PROTECTED]> wrote:
On Mon, Aug 14, 2006 at 07:13:53PM +0200, Yannick Lecaillez wrote:
> Patrice Dumas wrote:
>
> The idea is interesting but i don't know if its the nicest way to do
> that. Why not simply put KDB_DB_SYSTEM & KDB_DB_USER into config.h ? I

Since kdbprivate.h is shipped, it cannot rely on flags passed through
by config.h. That's why I did that. But if it is really private it may
be in config.h, but it shouldn't be mentionned in kdbprivate.h al all...

> Moreover, this could give use some ./configure --with-db-system=/etc/kdb
> --with-db-user=.kdb/

This is also easily doable with something along what I did.

--
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

Reply via email to