> Sure. Any ideas how to get the best of both worlds? If the problem is to avoid loading the wrong plugins, there are some options:
1. separate subdirs for each plugin type 2. the well-known function name can differ from app to app 3. let the user choose which ones to put in the subdir like everyone else does. In the rare case where a specific project needs a plugin, being able to manually load a .so that *isn't* in the right directory might be useful. Alternately, some auto-load feature that tries to be intelligent about loading plugins by guessing their names, or have each .so need a same-named peer .conf that can be pre-read to get configuration and use information. Then you know when to load the .so. Most apps just pre-load any available plugins, though. _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user