From: Ralf Angeli <angeli@caeruleus.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: auctex-devel@gnu.org, 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: Sat, 08 Dec 2012 12:25:51 +0100 [thread overview]
Message-ID: <87hanwu6o0.fsf@caeruleus.net> (raw)
In-Reply-To: <87hao0mw44.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Wed, 05 Dec 2012 15:06:35 +0100")
* Tassilo Horn (2012-12-05) writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Use elpa/packages/auctex as the official upstream.
>>
>>> We are planning to migrate to some DVCS anytime soon, but since
>>> AUCTeX is expected to work with all Emacs versions >= 21.x plus
>>> XEmacs >= 21.4.x, there's no way to develop it only as a part of
>>> emacs in its bzr repo, although that would be very nice from a
>>> maintenance point of view.
Since we want to make standalone releases for older Emacsen and XEmacs,
we'd also have to keep the build system.
>> I don't see what prevents it. AFAICT it still contains all the
>> backward compatibility code that's in CVS and nobody asked to remove
>> it. If there are a couple more xemacs-specific files, I have no
>> objection to you adding them.
>
> I'd welcome this but David and Ralf are more qualified to judge about
> feasibility. Especially, there's much complexity in auctex's build
> system in order to compile XEmacs packages, and that's a bit more than
> just an auctex-compat.el.
Another reason to keep the build system is the possibility to install
preview.sty and its documentation in a TeX system tree. You can do this
with `preview-install-styles' as well, but only for your user, unless
you have sudo or root access. So I dunno if a site-wide install of
AUCTeX and preview would be easily feasible with just the Emacs package
system.
>> The only remaining problem I can imagine is for those few files which
>> aren't FSF-copyright and hence aren't in the ELPA package, but IIUC
>> these are obsoletish and could just be dropped (noone complained about
>> them missing from the ELPA version).
>
> Yes, these 5 or 6 files are only addons for some special latex styles.
> They are not important for auctex, and they could be dropped or easily
> rewritten by someone else with CA by just looking at the corresponding
> latex style but not the current code.
If we don't get the CAs I wouldn't mind either deleting those files.
--
Ralf
prev parent reply other threads:[~2012-12-08 11:25 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 ` [AUCTeX-devel] " Uwe Brauer
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 ` Ralf Angeli [this message]
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=87hanwu6o0.fsf@caeruleus.net \
--to=angeli@caeruleus.net \
--cc=auctex-devel@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).