Summary: | No tomcat-4.1.29 ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Curtis Stanford <curtis> |
Component: | New packages | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | corporate_gadfly, wendywds |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 26994 | ||
Attachments: | Tar file containing tomcat-4.1.29 ebuild and supporting files |
Description
Curtis Stanford
2003-10-31 10:37:46 UTC
Created attachment 20021 [details]
Tar file containing tomcat-4.1.29 ebuild and supporting files
untar this file in /usr/local/portage/net-www/tomcat and you should be able
to
emerge it (assuming you have PORTAGE_OVERLAY set correctly).
Turning out to be a rather sad state of affairs. On Wed, Dec 3rd, Tomcat 5.0.16 stable was released. http://jakarta.apache.org/tomcat/tomcat-5.0-doc/RELEASE-NOTES.txt Moving this again to java@gentoo.org, so everyone out there can help. Tomcat 5.0.18 released: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/changelog.html Looks like quite a few bug fixes when going from 5.0.16 to 5.0.18. Two things: 1. It's important to support both the 4.1 releases and the 5.0 releases. Lots of people are not ready to move to 5.0 (it's a different servlet API version). 2. Let's get this tomcat 4.1.29 ebuild into portage -- it seemed to work well for me, and if it goes into ~arch masking, others will test. In my opinion, fixing this bug should make bug #26994 obsolete (you could mark that one WONTFIX or similar). Tomcat 4.1.29 and 5.0.18 are in portage now. Cheers, and thanks. Any new bugs, please post and we'll take care of it. Sorry for the slowness :( |