unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
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: Thu, 06 Dec 2012 10:46:34 +0900	[thread overview]
Message-ID: <87hao02br9.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <jwvmwxstu2q.fsf-monnier+emacs@gnu.org>

Stefan Monnier writes:

 > Can you describe how does the XEmacs-package-building relates to the
 > VCS repository?

It doesn't restrict the repository in any way.  The XEmacs package
build system puts the packages into a specific layout (basically
similar to an installed GNU Emacs of 19.x vintage, without the bin
directory and with no libraries in the top level of the lisp/
directory, only subdirectories containing packaged libraries).  The
build system has sufficient flexibility to handle the AUCTeX source
layout, and any future variation of it that I can imagine without
hallucinogens.  Updating it to handle future changes to AUCTeX's
source layout is *purely* our problem.

AUCTeX's build system does the same job in a different way.  The two
systems have different purposes.  AUCTeX's is to avoid a requiring
that its users and developers maintain a specific build environment
just for XEmacs packages.  Ours is to guarantee that our distributed
packages are built in a controlled environment.

As far as I can see, neither of these should affect GNU Emacs or GNU
ELPA for quite a while.  I think the Emacs maintainers should be
vaguely aware of the build environment issue, because there's a
possibility that as ELPA expands and becomes widely used,
inconsistencies among packages distributed stand-alone may arise.

However, since Emacs has a policy of eschewing support for non-GNU
systems when that conflicts with the optimal support for GNU, I think
ELPA will find it much easier to support AUCTeX's build system
directly.  It's difficult for us because it depends on utilities that
are normally not present on Windows, for example.

  parent reply	other threads:[~2012-12-06  1:46 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 [this message]
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=87hao02br9.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --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).