unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Didier Verna <didier@didierverna.net>
To: David Kastrup <dak@gnu.org>
Cc: auctex-devel@gnu.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 18:22:06 +0100	[thread overview]
Message-ID: <muxk3swo1mp.fsf@didierverna.net> (raw)
In-Reply-To: <87624gcuqw.fsf@fencepost.gnu.org> (David Kastrup's message of "Wed, 05 Dec 2012 17:46:15 +0100")

David Kastrup wrote:

> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

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

> No.  XEmacs was supported after the CVS layout had been established.  An
> XEmacs package is assembled in a target directory hierarchy separate
> from the source tree.

>> Are those requirements incompatible with the ones for ELPA packages?
>
> No idea.

  Not sure how this would work for a complex thing such as AUCTeX, but
  most of the time, it's not so difficult to support all those
  installation schemes from a single source tree.

  The key to packaging for XEmacs is that you need to provide a specific
  Makefile (sort of imposed by the infrastructure) with some predefined
  variables that you need to fill in. But the underlying organization of
  your source tree is pretty much what you want.

  Because the Makefile is specific, it's better to export your source
  tree to another directory (as David says) for XEmacs packaging. For my
  own packages, I have a generic infrastructure that does this. Every
  project contains a file named Makefile.pkg which is the XEmacs package
  one. I use 'hg convert' to export the tree to the appropriate place
  (XEmacs packages are under Mercurial) with a special .hgfilemap
  containing essentially this:

rename Makefile.pkg Makefile

  but the rest of the source tree remains mostly the same. I like to
  organize my tree with lisp/*.el doc/*.texi etc/stuff etc., but you
  could also be plain flat of whatever.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com



  reply	other threads:[~2012-12-05 17:22 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                   ` Didier Verna [this message]
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=muxk3swo1mp.fsf@didierverna.net \
    --to=didier@didierverna.net \
    --cc=auctex-devel@gnu.org \
    --cc=dak@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).