|--==> "SJT" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
>>>>>"SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> - They install to /site-packages/
SJT> Er, how do we do this currently?
Simple answer... we don't. We can't do it with PUI anyway (until I
extend it to cope). The way I see it, the developers of these types
of packages currently have two choices:
1) Distribute the package as a source tarball and the user
does a 'make install'. The install Makefile target would
compute the value of 'emacs-roots' and install to
${emacs-roots}/lib/xemacs/site-packages/ (they could also
go in ~/.xemacs/site-packages/)
2) Distribute the package as a binary tarball who's top level
directory is site-packages/. With instructions for the
user to unpack to either ${emacs-roots}/lib/xemacs/ or
~/.xemacs/
SJT> In particular, make bindist doesn't understand the difference
SJT> among {xemacs,mule,site}-packages..
'make bindist' doesn't need to make a distinction between the various
package directories. In the top level of a binary package tarball
you'll see:
etc/
info/
lib-src/
lisp/
man/
pkginfo/
Not: {xemacs,mule,site}-packages/
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|