>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)srce.hr> writes: 
    Hrvoje> A so-called "SUMO" tarball containing (almost) all the
    Hrvoje> packages has been planned.  The specifics have not yet
    Hrvoje> been agreed on, but I think the complete tarball will
    Hrvoje> exist.
That would be cool.
>>>> "sb" == SL Baur
<steve(a)vmailer.xemacs.org> writes: 
    BAW> > I know next to nothing about how the new package stuff
    BAW> works, but even > so, it was pretty painless for me get the
    BAW> packages I wanted installed > and working with XEmacs 21.  It
    BAW> worked very well in my strange > /depot/gnu installation :-)
    BAW> Kudos to all!
    sb> Cool!
Very!  I was quite impressed.
    sb> Formal uninstallation support is lacking at present.  It
    sb> hasn't been forgotten and there will be some support by
    sb> release time.  One of the Golden Rules of packages is that
    sb> `leaf' regular packages (like Supercite) may have all their
    sb> installed files deleted without harm.  Individual .el files in
    sb> single-file packages may be deleted without harm (like
    sb> lazy-lock.el in the edit-utils package).
I would imagine that uninstalling will happen far less often than
updating, or even checking for currency.  I'd really love to have a
tool (either lisp or command-line, but probably the former), that I
could run now and then, that would spit out lines like: "you have an
out-of-date CC Mode package, please upgrade".  I don't even mind doing
all the ftp's myself!
    sb> There's a naming convention to allow Mule packages to coexist
    sb> with non-Mule XEmacs builds.  Put your non-Mule packages in
    sb> `xemacs-packages' and your Mule packages in `mule-packages'.
    sb> Any packages in a `mule-packages' hierarchy are left untouched
    sb> in a non-Mule XEmacs.
Thanks for the info on this.  Hopefully there'll be a nice document on 
the Web site that is "brain-dump-of-hrvoje-and-steve.html" :-)
BTW, I wonder if Eric Raymond's Trove project might not help in
managing the lisp packages.  I don't follow Trove development, but if
Eric's involved it must be cool.  It may be too early to capitalize on 
the Trove work, but in any event, here's a pointer to Eric's pages:
    <
http://tuxedo.org/~esr/trove/>
-Barry