>>>> Hauke Fath <hf(a)spg.tu-darmstadt.de> writes:
pkgsrc ships an "xemacs" (21.4) or
"xemacs-current" (21.5) package, and
an "xemacs-packages" package. The latter until noe only untared the
individual xemacs package tarballs, and I am in the process of changing
that, in order to be able to patch individual distribution files.
I acknowledge the problem. I have similar problems with maintenance of
xemacs packages in Gentoo. There we handle the xemacs packages as
binary blobs (and as such can't easily be patched.)
You see, there is one supported way to build xemacs packages and that
is by using the xemacs package source tree. This includes the make
support with dependencies between packages etc so they are guarantied
to get right. That mixes badly with what you want to do as you have
noticed.
In Gentoo we have for now used the following compromise. If there are
packages that needs to be patched we try to get that patch into the
beta release of that package and use the beta package also in the
stable tree. It has its problems but requires little development on
our part.
I guess it is technically possible to do what you are attempting but
that is more or less constructing a new build system for the packages
isn't it? You can do that if you want but if you have full control of
your sources why don't you just clone the xemacs package tree and
patch it there and distribute your own versions of all elisp modules?
I also find that most patches are not distribution dependent and does
more good if they are contributed to the xemacs package tree and even
upstream to that.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta