Re: Future of XEmacs

Andreas Röhler writes: You're wrong. If you think otherwise, ask Norbert directly how much burden it is on him. For everybody else, 99% of their effort goes into implementing features and fixing bugs, and it would be even higher if we were doing a lot of development because people would be sufficiently in practice that they don't need to ask questions about who commits in the top-level. There are two real issues with packages. The first is the $prefix/lib vs. $prefix/share mess, which mostly affects users rather than developers, but needs fixed (and is gradually improving in 21.5). This is a difficult issue because it crosses versions, and 21.5 is not yet ready to replace 21.4 for many users. The other is the build-in-tree issue. This is a tradeoff; on the one hand, it does involve more developer resources, because you have to have the whole tree, keep it updated, and so on. On the other hand, it reduces the amount of resources required to work on core, and imposes a discipline on high-level APIs. I have no idea what you mean by that. I gather you haven't noticed ELPA yet, either. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta