Currently Gump is reporting that 'jakarta-tomcat-jk-native-configure' is failing, but this is really because 'jakarta-tomcat-jk-native-buildconf' is failing (but not with a status code, so Gump has no way of knowing this). The reason is that the buildconf.sh script depends on automake being installed. As I see it, there are three options:
1) Have some nice person install automake someplace where it will be in the $PATH when Gump runs.
2) Have some nice person install automake as an installed package, modify the metadata to <depend> on it, and modify the Gump code for <script> to place the <depend>s in the $PATH. This is like $CLASSPATH for <ant>.
3) Kill off jakarta-tomcat-jk-native*. Since mod_jk isn't really being developed for httpd/2.1.x, this isn't as drastic as it sounds.
the preferred "gumpy way" would be #2, but I could stick for both #1 and #2 either way.
i can do #1 in a second, I might need a little help for #2... also the question is: once we start with these native dependencies how far off should we go? OS? ;-)
-- Stefano.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
