Re: PUI manages 3rd party packages: more RPM or DEB like
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
>>>>> "Uwe" == Uwe Brauer
<oub(a)ucmail.ucm.es> writes:
Uwe> So here I have to chose one of the possibility mentioned
Uwe> above.
XEMACS_STAGING seems to be misdocumented. I'll get back to you on
that.
symlink=t is irrelevant to package distribution as tarballs. You
should physically copy the files to a clean staging directory for
that.
Uwe> This seems to be too bad. If I understand correctly a
Uwe> maintainer of a 3rd package has to make his decision where to
Uwe> install the package and there are pro and cons for either
Uwe> solution.
The maintainer of a 3rd party package has no choice about where to
install the package. It's the local admin's call. Ie, the minimal
package `foo' will contain in the tarball
lisp/ lisp/foo.el lisp/foo.elc lisp/auto-autoloads.el
lisp/auto-autoloads.elc pkginfo/ pkginfo/MANIFEST.foo
No "xemacs-packages/". Where those subdirectories reside is up to the
installing admin, not the package maintainer.
That was my understanding so far! In other words a 3rd party package
*can* be untarred, *either* in ~/.xemacs/xemacs-packages
*or* in
/prefix/lib/xemacs/site-packages
If so to include x-symbol, which is already in pkg format and is
tested for almost 2 years, would practically just mean to copy it in
the main package tree. I am pointing this out, because before
contacting Christoph I want to understand what has to be done.
Usually it was said CVS access and an appropriate Makefile,
Xemacs.rules file etc, but x-symbol is exceptional, since it is
already in pkg format. So it looks to me like to reinvent the wheel if
one does all this Makefile, rules thing.
However there is still something I fail to understand
in cHristophs Makefile for the source distribution there is line:
PACKAGEDIR = $(HOME)/.xemacs/xemacs-packages
What is this good for, if it does not matter, that the PACKAGEDIR
could also be
/prefix/lib/xemacs/site-packages
Thanks
Uwe