Re: Package Bug Reporting Suggestion

APA> How about something like this? APA> Index: package-ui.el Let's not limit this to packages. Replace the whole bug-reporting mechanism instead. OK, it makes sense to start with packages, but what should happen is there should be a database which maps module (usually, but not necessarily, packages) name-symbols to reporter functions. You don't need an address in the db for the generic "send it to XEmacs" function, because it's (format "%s-bugs(a)xemacs.org" pkgname). Other reporter functions should normally provide their own addresses. I guess it's reasonable for the package info to be put into package-info.in, and stored online in the packages-package-list database. Except that if the package is hosed, and that doesn't get autoloaded ... but that's not really an upstream problem. So I guess we can default to the generic reporter for that, since it's really an XEmacs bug if the package doesn't get autoloaded right. So the real dispatcher function shouldn't live in pui, it should live in core. Core should also have a minimal reporter function; we can have a fancy all-singing-all-dancing upgradable reporter in packages, too. The pui reporter should just be a thin wrapper over the real dispatcher. That way we always have the same UI, error handling, etc., whether bug reports are invoked from pui, M-x, or the Help menu. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.