From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.auctex.devel,gmane.emacs.devel Subject: Re: Updating the GNU ELPA package of AucTeX Date: Tue, 03 Sep 2013 16:19:03 +0200 Message-ID: <874na2q97s.fsf@fencepost.gnu.org> References: <878uzj639h.fsf@thinkpad.tsdh.org> <877gey9x8b.fsf@thinkpad.tsdh.org> <87wqmyqrkg.fsf@fencepost.gnu.org> <87txi28eko.fsf@thinkpad.tsdh.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1378217961 8256 80.91.229.3 (3 Sep 2013 14:19:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 3 Sep 2013 14:19:21 +0000 (UTC) Cc: auctex-devel@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: auctex-devel-bounces+gead-auctex-devel=m.gmane.org@gnu.org Tue Sep 03 16:19:24 2013 Return-path: Envelope-to: gead-auctex-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VGrRx-0000yF-41 for gead-auctex-devel@m.gmane.org; Tue, 03 Sep 2013 16:19:21 +0200 Original-Received: from localhost ([::1]:46442 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGrRw-0000bu-LO for gead-auctex-devel@m.gmane.org; Tue, 03 Sep 2013 10:19:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53874) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGrRt-0000Cd-UI for auctex-devel@gnu.org; Tue, 03 Sep 2013 10:19:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VGrRr-0006p1-Iw for auctex-devel@gnu.org; Tue, 03 Sep 2013 10:19:17 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:56246) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGrRr-0006ot-Gz; Tue, 03 Sep 2013 10:19:15 -0400 Original-Received: from localhost ([127.0.0.1]:35189 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGrRr-0005rR-0i; Tue, 03 Sep 2013 10:19:15 -0400 Original-Received: by lola (Postfix, from userid 1000) id E8BEFE08CE; Tue, 3 Sep 2013 16:19:03 +0200 (CEST) In-Reply-To: (Stefan Monnier's message of "Tue, 03 Sep 2013 09:48:14 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: auctex-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion list for AUCTeX developers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: auctex-devel-bounces+gead-auctex-devel=m.gmane.org@gnu.org Original-Sender: auctex-devel-bounces+gead-auctex-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.auctex.devel:3212 gmane.emacs.devel:163163 Archived-At: Stefan Monnier writes: >>> It is not clear to me why the act of importing a runnable version of >>> AUCTeX into ELPA should be precluded from running a Makefile rule. >>> It is not like ELPA can directly access git repositories and extract >>> whatever it wants, so the import will always involve explicit steps. > > Yes, GNU ELPA can and does "git pull" every day as part of its > automatic procedure. If it expects a package to be in a finished state upon pulling, it means that any standard GNU package (which requires ./configure && make && sudo make install to work) is not supported. The AUCTeX build procedure supports creating an XEmacs package. The XEmacs package is built using a system agnostic configuration which detects most things at runtime (at some cost). Basically you are asking that we throw away all configurability of AUCTeX and convert its repository into an installed tree with a "neutral" configuration. How will its Texinfo files get converted into documentation readable as PDF or info? How will its intro.texi get converted into README by makeinfo? After all, every GNU package should have a README, right? Our current procedures create this README. >> The new Git ELPA could have the savannah auctex repository as a >> submodule, so there wouldn't be two individual auctex repositories >> that need to me synchronized manually. > > That's the intention, indeed (tho not technically as a Git submodule, > but morally equivalent). "Morally equivalent"? You make it sound like you consider the current AUCTeX repository immoral. At any rate, it would be easy enough to create Makefile targets that would export a setup suitable for ELPA. It's not really superbly apropos The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. [...] The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. but of course, once you throw away any other way of configuring the package, what remains is by definition the "preferred form for making modifications" since nothing else exists anymore. > I'd be OK with splitting auctex into 2 packages, but does > preview-latex work without auctex? No. It would be nice to factor out some of its quite sophisticated functionality into something independent from AUCTeX, LaTeX and in fact also TeX, but at the current point of time preview-latex is not independently useful. -- David Kastrup