Uwe Brauer writes:
- the installation *needs* Latex, the Local.rules file has to
be
changed accordingly and Norbert must have latex installed on
his machine.
Do you mean *installation* or *build*? It's not a problem to require
LaTeX for compiling any AUCTeX-specific .tex files etc, which is part
of the *build*. But if you need to build in the location of TeX
binaries or libraries outside of the AUCTeX package, it's a
showwtopper IMO.
- the procedure of generating the auto-autoload.el files had
changed completely and proved to be the major headache. Now the
only solution so far is to modify Xemacs.rules.[1]
I don't think this is a problem in principle (the JDE support is much
more horrifying :-), but I have some questions about the patch.
EXTRA_AUTOLOADS_DEPENDENCIES is independent of
GENERATED_ELC_DEPENDENCIES, right? If so, you shouldnt substitute the
first for the second. Both should be present.
Also, where are EXTRA_AUTOLOADS_DEPENDENCIES and
GENERATED_ELC_DEPENDENCIES set? This should be be documented.
I would like to hear opinions about that issue and finally receive
an
approval for the Xemacs.rules patch because otherwise auctex cannot be
synchronized. We can continue the discussion on xemacs-patch if that
is more appropriate.
- Finally I would like to ask an advice concerning CVS. The
structure of the auctex tree has changed considerably. Of
course I could use
cvs add newfile
cvs remove oldfile
This is much preferable. Although CVS won't preserve history, when we
move to a more capable version control system the migration script
will see the remove/add pair and do the right thing. You can automate
this with a shell function
function cvs-move () {
oldfile=$1
newfile=$2
mkdir -p `dirname $newfile`
mv $oldfile $newfile
cvs remove $oldfile
cvs add $newfile
cvs commit -m "Move $oldfile to $newfile." $oldfile $newfile
}
The reason for doing the actual commit in this way is to help
migration scripts, which often look at the log message to identify
changesets that go together. It is also a very good idea to do all
the mv'ing in one session, based on moving the current versions of the
files, and tag the workspace both before and after. Eg,
cvs tag -c pre_Great_AUCTeX_11_84_Move
cvs-move A B/C
cvs-move D B/E
cvs-move F G/H
.
.
.
cvs tag -c post_Great_AUCTeX_11_84_Move
Then update to the new versions and add new files
rsync -av AUCTeX-11.84 AUCTeX-XEmacs
cvs add any new files not part of the move
cvs commit -m "Sync to AUCTeX 11.84."
cvs tag -c post_AUCTeX_11_84_Sync
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta