[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Splitting of XEmacs21 elisp packages

I've made a first rough version of a splitting of
xemacs21-{base,mule}support into individual packages.  These packages
are at

  deb http://people.debian.org/~schepler/ xemacs21/

along with updated versions of a few packages which previously ignored
the xemacs21 flavor.

Note this is not for the faint of heart; it still has serious
problems.  Among the problems I'm aware of:
* There are too many strong dependencies.  Because of this, a
  majority of the packages have to be installed anyway to satisfy
  the dependencies.  I need to figure out which dependencies can
  be reduced to Recommends or Suggests.
* Some of the packages are probably missing dependencies on external
  programs that are needed.
* Some of the packages might be useless for Debian systems, or might
  need to be moved to contrib.
* Gnus isn't getting its autoloads registered for some reason.
* mh-e is refusing to install at all, failing to load "gnus-util".

If anybody is willing to risk breaking an XEmacs installation, I'd
appreciate hearing how it goes.  (Having given all these caveats,
though, I _am_ writing this message using the new packages.)

One thing I haven't decided yet: how should other packages make sure
the appropriate packages are installed?  So far, the best idea I've
come up with is to create a dummy package "no-xemacs21" which
conflicts with xemacs21, so that a package could for example declare

  Depends: emacsen, no-xemacs21 | xemacs21-mail-lib,
           no-xemacs21 | xemacs21-fsf-compat

This seems ugly, though.
Daniel Schepler              "Please don't disillusion me.  I
schepler@math.berkeley.edu    haven't had breakfast yet."
                                 -- Orson Scott Card

Reply to: