* Wed 2000-01-19 Valdis.Kletnieks(a)vt.edu list.xemacs * Message-Id: <200001191028.e0JAScp04514(a)black-ice.cc.vt.edu&gt; | It's not a question of the package system.. The issue is the 'awkward | code bloat' that Adrian mentions. At some point, you have to just | say "screw it, Foobar-1.19 wirls on 21.2.19 and laoter only, you | 21.1 users are stuck with Foobar-1.18", or you have to endure code | that keeps accumulating more and more (if featurep()) code all over | the place. | | For an interesting time, cd to xemacs-packages/lisp, and try this: | | find . -name '*.el' | xargs grep -i lucid | more If I may say opinion on this, having coded for several Emacs releases and supporting both Emacs and XEmacs. To my opinion the right thing to do is to provide compatibility functions (preferrably in separate package, like fsf-compat) And have the code run with the latest functions and parameters. If someone uses older Emacs, he is instructed: Get the compatibility package Or Get older version of the package (and be stuck with it until you upgrade XEmacs) This way the code does not suffer from old lag. Using the latest makes the code also cleaner and easier to maintain. jari