>>>>> "Raif" == Raif S Naffah <[EMAIL PROTECTED]> writes:
Raif> what safe assumptions can we make for non-Eclipse users; e.g. a Debian Raif> packager who requires the sources as well to patch them when addressing Raif> security issues (see mail in Raif> http://developer.classpath.org/pipermail/classpath/2006-July/001136.html)? I don't think there is a problem here. Maybe I'm misunderstanding though... The Classpath javah depends on having an ASM jar file around, both at build time and at runtime. (I neglected the runtime part in the wrapper script in yesterday's patch -- I fixed it here.) By default Classpath simply won't build javah. If you specify --with-asm, it will. So all Debian has to do is package ASM and make it a build dependency of Classpath. This introduces a package cycle, but distros already have to deal with those all the time... The Eclipse-based build is different, I think. It is for developers really; I doubt any distro would (or could) use that. Tom
