unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: David Kastrup <dak@gnu.org>
Cc: auctex-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: [ELPA-diffs] /srv/bzr/emacs/elpa r312: Update AUCTeX ELPA package to the new 11.87 release.
Date: Wed, 05 Dec 2012 10:14:39 -0500	[thread overview]
Message-ID: <jwvmwxstu2q.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ip8gd1al.fsf@fencepost.gnu.org> (David Kastrup's message of "Wed, 05 Dec 2012 15:24:50 +0100")

> The XEmacs package building is sort of an aggravation.  An XEmacs
> package contains all necessary files plus info source files in a rigid
> directory layout, possibly not unsimilar to what ELPA or any other
> package would do.

Can you describe how does the XEmacs-package-building relates to the
VCS repository?  Is it that the CVS layout was chosen specifically to
match the XEmacs package requirements?  Are those requirements
incompatible with the ones for ELPA packages?

> So it is not clear to me who the customers for the XEmacs packages we
> compile actually are.

I'll let the AUCTeX maintainer(s) decide whether it's important to
support this.

> 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.

If a file is in `elpa/packages/auctex' then it will be in the ELPA
package (which is little more than a tarball of that directory).
But I don't see why including prv-xemacs.el in the ELPA package would be
a problem.  It's arguably wasteful, but I doubt anybody cares.

This said, we could tweak the GNU ELPA build scripts so that some files
are removed from the tarball.


        Stefan

  parent reply	other threads:[~2012-12-05 15:14 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 [this message]
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=jwvmwxstu2q.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=auctex-devel@gnu.org \
    --cc=dak@gnu.org \
    --cc=emacs-devel@gnu.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).