Am Montag, 31. Juli 2006 01:49 schrieb Yannick Lecaillez: > * An installable form : configure script check if a libltdl is > existing. If yes it will use it. Otherwise, it will compile and install the > embeded libltdl on the system and then use it. Note this mode need > to keep the embeded form of libltdl too.
Are you sure it works out? On my system it always configures the libltdl, but I should have one on my linux box, or? > I made the choice to always use the embeded form for > dependency/simplicity reason (here, libltdl is in /usr/lib) > You can found more information about that here : > http://www.gnu.org/software/libtool/manual.html#Distributing-libltdl I think this choice is completely correct. > I think that's not as dirty as it could look. Indeed, today most > settings are simply hardcoded. Imho that's more dirty than have a > configuration file. We should look at the configuration points in special. Which hard coded things are a problem? > If i would store my entire configuration stuff into /config/ for some > reason, i have to recompile backends. There is actually no flexibility. The unix pathes are hardcoded, like /bin, /lib, /etc There is not really a problem with it... > Defining default backend using symlinks rather than fetch its name from > a configuration file is dirty too for at least two reasons : I would see elektras future in having a root (or default) backend (which will be filesys?) and mounting other backends into it. This would enable many backends on one computer, up to one backend per path or app. And it would make it possible to use a daemon, but also the same namespace during bootup (then you could/should not access pathes which need the daemon). > * Imagine you want to change default backend (like hot-plug) : have to > remove and recreate the symlinks could produce some strange behaviour. This would kill all the old configuation. You have to export and import the config to do that. So situation now is not really backend changeable. > With an elektra configuration file, you could simply edit it and change > the default backend's name. Then, eventually, send a -HUP to running > applications and things will simply works as expected. There is still a > race condition, but this one could be simply removed using locking. You are right that elektra is not able to change a used backend by now. The symlink should be removed. But I don't think that the configuration file will save the day;) > Perhaps this idea > http://article.gmane.org/gmane.comp.lib.elektra.devel/23 is a bit "too > much" today. We could simply begin with a "dumb" flat configuration file > and start to define a scheme for allowing elektra and backends to have > some "dynamic" parameters. Don't think that getting configuation files for elektra is a good idea. thank you Markus Raab ------------------------------------------------------------------------- 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
