all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: Re: documentation on how to add packages to ELPA?
Date: Sun, 22 Dec 2013 20:24:31 -0500	[thread overview]
Message-ID: <jwvsitkbc4g.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <85lhzdw1lc.fsf@stephe-leake.org> (Stephen Leake's message of "Sun, 22 Dec 2013 05:45:51 -0600")

> How do I specify package metadata such as min and max Emacs version,
> since I don't write the define-package args?

The dependencies are specified in the "Package-Requires:" pseudo-header
(grep for it in elpa/packages/*.el to see examples).

> Where is the "Version:" psuedo-header defined? Is it just
> ;; Version: 5.0

Yes.

> or more complex?

No.  It's the format understood by the lisp-mnt.el package, and used by
ELPA single-file packages.

> Is there metadata support for "optional" as opposed to "required"
> packages?

No.  The purpose of "Package-Require" is to help the user install
the package.  If it's optional, then it's simply not required.

> Should the build and test files be included in Gnu ELPA?

If at all possible (i.e. if the copyright status is clear), then please
do include them in the `elpa' branch, yes.

If you don't want all files included in the tarball distributed on GNU
ELPA, you can use a .elpaignore file (see js2-mode/.elpaignore for the
only existing example so far).


        Stefan



  reply	other threads:[~2013-12-23  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21 23:08 documentation on how to add packages to ELPA? Stephen Leake
2013-12-21 23:34 ` Jambunathan K
2013-12-22  0:01 ` Xue Fuqiao
2013-12-22 10:46 ` Stefan Monnier
2013-12-22 11:45   ` Stephen Leake
2013-12-23  1:24     ` Stefan Monnier [this message]
2013-12-23 22:58       ` Xue Fuqiao

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvsitkbc4g.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.