Stephen J. Turnbull writes:
>>>>> "Uwe" == Uwe Brauer
<oub(a)ucmail.ucm.es> writes:
Uwe> I have to discuss this with Christoph of course; in principle
Uwe> yes, however I consider x-symbol as a rather sophisticate
Uwe> package quite beyond my lisp knowledge and I am not sure that
Uwe> I am qualified for this.
I think you're misunderstanding the role of the third party maintainer
here.
Hello
I already told Ville, that I would volunteer maintaining the AUCTeX
package since it is very outdated; concerning preview-latex and
x-symbol let us put them aside for the moment.
However I would, at least, partially understand what I am doing, so
here are a couple of questions, some are of technical, some of
'political' nature (some of my questions will be very basic, but I
never really worked for example with cvs)
1. The relation between 3rd party packages and offical one: You
already wrote that it is important were such package are generated,
however you said, a package could be installed in
/prefix/xemacs/xemacs-package
or
~/.xemacs/xemacs-package
or
/prefix/xemacs/site-packages
If so why does Christophs Makefile contain the line
PACKAGEDIR = $(HOME)/.xemacs/xemacs-packages
(his package is supposed to be installed in this directory)
but I could not find such a target in the Makefiles of the CVS, I
downloaded (see below)
Political question: suppose I generated a new AUCTeX package could
this also be put on the official AUCTeX page or is there a danger that
it will be considered as a 3rd party pkg and installed in
~/.xemacs/xemacs-packages
2. I tried first to built up the existing 1.33 AUCTeX package, based on
10g, before going to the 11.13 version, I want to be sure that I
did correctly
I first downloaded the cvs tree, by
cvs -d:pserver:cvs@cvs.xemacs.org:/pack/xemacscvs login
cvs -f -z3 -d:pserver:cvs@cvs.xemacs.org:/pack/xemacscvs checkout -P xemacsweb
cd xemacsweb/
cvs co packages
cvs co package-control
cd packages/
cvs co xemacs-base
cd xemacs-base/
make
cd ..
cd auctex/
make
It did not work for my 21.4.12 no mule version!!! I frequently download
and compile AUCTeX myself and never had this kind of problem. While
xsymbol detects whether a mule or no-mule version is used, I am not so
sure about AUCTeX, I have to ask David, but I want to know whether a
-with-no-mule compiled AUCTeX would run under mule and vice
versa. I expect that a -with-mule compiled AUCTeX would run with no
mule and *not* vice versa.
I personally don't use Mule, but think the AUCTeX should be compiled
such that it is usable for both.
3. The make process worked for xemacs-21.4.12 with mule, but no
binball was generated. I thought the generated binball would be in
/tmp/stagging??
4. Windows version. Can the generated AUCTeX package be used for the
Win9x/NT/2000/etc version of Xemacs or do I have to compile another
one??
Regards
Uwe