Re: Stop building 21.5 nomule

Stephen> The problem is that having coding cookies in the Stephen> xemacs-packages hierarchy implies calling a Mule API in a Stephen> no-Mule XEmacs. The only way to fix that is to remove Stephen> support for no-Mule builds. What about an error message when a non-mule XEmacs finds a coding cookie then? XEmacs eating all CPU endlessly or crashing due to SEGV doesn't seem that user friendly. [...] Stephen> No coding cookies, and files are ISO-8859-1 has been the Stephen> policy for the xemacs-packages hierarchy since it was Stephen> invented. If this is going to be a problem for the package Stephen> maintainer, we move the package to mule-packages. That's Stephen> precisely why we have mule-packages. OK. So either the offending packages need to go strictly ISO-8859-1 or move out to mule-packages. Right? Yours -- %% Mats