been in ~arch since July. Should be good to go, not directly easy to test. Basically need to emerge either Tomcat 5.5.x or 6.x, then edit /etc/conf.d/tomcat-* to load the .so. You can then confirm in log file in /var/log/tomcat-* if the native library was loaded or not.
amd64 stable
x86 stable and closing
(In reply to comment #1) > amd64 stable > it's not betelgeuse@pena /usr/portage/dev-java/tomcat-native $ eshowkw Keywords for dev-java/tomcat-native: | s | | p p | | p a x | | c r 8 | | - c 6 | u | a a m p s - - | n | l m h i m m a p s p f f | u s | p d a p a 6 i p c c 3 a b x b | s l | h 6 r p 6 8 p p o 6 9 s r s 8 s | e o | a 4 m a 4 k s c s 4 0 h c d 6 d | d t ----------+---------------------------------+---- 1.1.8 | + + | 0 1.1.10 | ~ + | 1.1.12 | ~ ~ | * 1.1.13-r1 | ~ ~ | 14:19 < uprooter> INFO: An older version 1.1.8 of the Apache Tomcat Native library is installed, while Tomcat recommends version greater 14:19 < uprooter> then 1.1.10 14:19 < uprooter> is it considered a bug ?
(In reply to comment #3) > (In reply to comment #1) > > amd64 stable > > > > it's not It was, or at least should have been. Looks like I missed the stable keyword in commit. Not sure how that happened, but seems to be the case per cvs. 12 Oct 2007; William L. Thomson Jr. <wltjr@gentoo.org> tomcat-native-1.1.8.ebuild, tomcat-native-1.1.10.ebuild: amd64 stable, bug #195576. Added quotes. Likely moot at this point since we will be stabilizing a newer version per bug 209410.
Definitely moot since we are stabilizing 1.1.13 on bug 209410. Moving back to fixed. Will remove <1.1.12 or possible < 1.1.13 once 1.1.13 is stabilized.
