From: Uwe Brauer <oub@mat.ucm.es>
To: David Kastrup <dak@gnu.org>
Cc: auctex-devel@gnu.org, xemacs-beta@xemacs.org,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: [AUCTeX-devel] [ELPA-diffs] /srv/bzr/emacs/elpa r312: Update AUCTeX ELPA package to the new 11.87 release.
Date: Wed, 05 Dec 2012 15:39:02 +0100 [thread overview]
Message-ID: <87vccgbm2h.fsf@gilgamesch.quim.ucm.es> (raw)
In-Reply-To: <87ip8gd1al.fsf@fencepost.gnu.org> (David Kastrup's message of "Wed, 05 Dec 2012 15:24:50 +0100")
>> On Wed, 05 Dec 2012 15:24:50 +0100, David Kastrup <dak@gnu.org> wrote:
> Tassilo Horn <tsdh@gnu.org> writes:
[snip]
> Now XEmacs will only distribute package files that have been assembled
> by XEmacs tools in the XEmacs package tree.
This is correct. I wish it were different, that there
existed a debian-like-alien tool which allowed to convert
one package into another one, like deb-->rpm
> So the XEmacs packages that AUCTeX provides will work
> fine, but you'll have to find, download and install
> them manually instead of relying on the XEmacs
> packaging system.
You can unpack it in ~/.xemacs/packages
or in
prefix/xemacs/site-packages
> What will be provided in the XEmacs package
> repositories consequently is something massaged
> manually to the necessary layout, commonly with
> mistakes and several years behind.
Well if their package manager were faster it should be a
question of days not years :'(
[snip]
> The XEmacs compatibility code in the Lisp files itself is peanuts in
> comparison. No point in removing that as far as I can see. However,
> preview-latex has a somewhat more extensive compatibility setup. It
> would be arguable not to place the prv-xemacs.el files in the ELPA
> packaging at least.
That is your call to make.
> Removing it from the source distribution would be
> seriously unfair since it is technically complex enough that starting it
> from scratch would be quite hard: that would be several man-months at
> least from an experienced XEmacs programmer, and there are none as far
> as I can see interested in AUCTeX.
Yes, please, do *not* remove it, that would be real nightmare
for Xemacs users.
Uwe Brauer
next prev parent reply other threads:[~2012-12-05 14:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1TfF2V-0003Gn-No@vcs.savannah.gnu.org>
2012-12-03 20:40 ` [ELPA-diffs] /srv/bzr/emacs/elpa r312: Update AUCTeX ELPA package to the new 11.87 release Stefan Monnier
2012-12-04 7:29 ` Tassilo Horn
2012-12-04 14:50 ` Stefan Monnier
2012-12-04 20:34 ` Tassilo Horn
2012-12-04 21:26 ` Stefan Monnier
2012-12-05 14:06 ` Tassilo Horn
2012-12-05 14:24 ` David Kastrup
2012-12-05 14:39 ` Uwe Brauer [this message]
2012-12-05 15:14 ` Stefan Monnier
2012-12-05 16:46 ` David Kastrup
2012-12-05 17:22 ` [AUCTeX-devel] " Didier Verna
2012-12-05 18:36 ` Stefan Monnier
2012-12-06 1:46 ` Stephen J. Turnbull
2012-12-15 14:08 ` Tassilo Horn
2012-12-08 11:25 ` [AUCTeX-devel] " Ralf Angeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vccgbm2h.fsf@gilgamesch.quim.ucm.es \
--to=oub@mat.ucm.es \
--cc=auctex-devel@gnu.org \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=xemacs-beta@xemacs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).