Another suggestion for the db-3/db-4 ebuild would be a check for emerging of db
outside of the initial stage1 build. If this was true, a subsequent check for
the "java" and "tcltk" USE keywords would then be made.
If "java" was found, it would generate the appropriate dependancies [jdk] and
build the java API by passing "--enable-java" to the configure line.
If "tcltk" was found, it would generate the appropriate dependancies [tcl] and
build the tcl API by passing "--enable-tcl" to the configure line.
The latter would be particularly handy in that it would allow the building and
execution of the berkeley db testsuite to verify the core API's via the "--
enable-test" flag [for sandbox only, as sleepycat doesn't reccomend distro'ing
the libs built with this flag].
More info at the url provided...
This seems easily doable. I'm a little weary of the notes about Java support:
Before configuring, you must set your PATH environment variable to include
javac. Note that it is not sufficient to include a symbolic link to javac in
your PATH because the configuration process uses the location of javac to
determine the location of the Java include files (for example, jni.h).
I think with some JDKs javac is a symlink and with some it isn't. Any java guys
want to chime in?
Reassigning bugs due to lack of time.
db-4 should work with java and tcltk support, and has it in useflags. Official inclusion is just depending on fixing some other packages to correctly detect db4 with versioned symbols.
Do you think we need to add support for java and tcltk in db3 too?
I guess I can close this bug