Re: JDE bug in jde-build-classpath

Philip> [Don't know whether this should go directly to JDE team or Philip> not, please enlighten me....] If you believe it's purely a JDE bug, send it to them, only, with a couple of exceptions. All XEmacs packages have ＠xemacs.org aliases of the following form: $package-bugs, $package-discuss, $package-patches, $package-maintainer. Here, the relevant alias is jde-bugs(a)xemacs.org. For your convenience, these aliases get redirected appropriately, in this case to jde(a)sunsite.auc.dk. Many packages have no maintainer of record, so they go to xemacs-beta at the moment. This will eventually change to a real xemacs-bugs address. The exceptions are (1) if you believe that it's an XEmacs incompatibility, in which case we should know about it too. We have to negotiate these with the upstream maintainers and the GNU Emacs maintainers. This case might fit that (if jde-normalize-path just wraps XEmacs functions to do the real work). When in doubt send to both. And (2) if it's a real showstopper, in which case XEmacs might make a change to our package before a release of an official fix. However, upstream maintainers really hate this, so it's pretty rare. On a few occasions where you can show it's clearly an XEmacs bug, but was originally triggered in the context of a package, you may wish to send a courtesy copy to the package maintainers so that they are aware of your analysis in case they get reports of the bug. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.