DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18675>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18675 clean up getopt(s) section of runConfigure ------- Additional Comments From [EMAIL PROTECTED] 2003-04-04 15:44 ------- I guess I wouldn't say it's a "must have", but it seems like the rules for a code freeze might be bent for such a change since it seriously affects portability and does not affect the actual codebase. Granted, testing would be a necessity. The argument for including it immediately would be to improve portability. Among the web development community local to me, Xerces/Xalan have a reputation for being difficult to build (especially when trying to build the corresponding Perl modules). I would say any portability enhancements would be strong improvements. The argument for waiting would probably be that, once recognized, there's an easy workaround. Obviously, the decision will rest with the developers, though (one of whom I'm not, yet).
