From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Supporting multiline Package-Requires header
Date: Mon, 10 Aug 2015 18:05:08 -0400 [thread overview]
Message-ID: <jwv8u9iiyxu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <877fp3dxt2.fsf@gmail.com> (Thierry Volpiatto's message of "Mon, 10 Aug 2015 16:26:33 +0200")
> I suggest keeping what we have actually for backward compatibility and
> generalize the use of a *-pkg.el file with a define-package form even
> for single file packages.
How would that work? I mean a single-file package, as the name implies,
is made up of a single file, so where would you put the *-pkg.el?
Stefan
PS: FWIW, the elpa.git source code used to make GNU ELPA's packages
doesn't use *-pkg.el files (instead they're built from the lisp-mnt
headers when constructing the tarball).
next prev parent reply other threads:[~2015-08-10 22:05 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 11:12 Supporting multiline Package-Requires header Artur Malabarba
2015-08-10 11:42 ` Kaushal
2015-08-10 11:59 ` Artur Malabarba
2015-08-10 12:05 ` Phillip Lord
2015-08-10 12:28 ` Artur Malabarba
2015-08-10 12:51 ` Phillip Lord
2015-08-10 13:08 ` Artur Malabarba
2015-08-10 13:54 ` Bozhidar Batsov
2015-08-10 15:22 ` Artur Malabarba
2015-08-11 21:05 ` Phillip Lord
2015-08-11 21:48 ` Artur Malabarba
2015-08-12 5:34 ` Bozhidar Batsov
2015-08-12 14:09 ` Stefan Monnier
2015-08-12 14:23 ` Artur Malabarba
2015-08-12 17:18 ` Stefan Monnier
2015-08-12 20:10 ` Artur Malabarba
2015-08-13 18:13 ` Artur Malabarba
2015-08-13 20:44 ` Stefan Monnier
2015-08-13 22:37 ` Rasmus
2015-08-13 23:01 ` Artur Malabarba
2015-08-14 0:12 ` Rasmus
2015-08-14 1:42 ` Stefan Monnier
2015-08-17 18:45 ` Achim Gratz
2015-08-18 15:56 ` Stefan Monnier
2015-08-18 18:00 ` Achim Gratz
2015-08-19 17:14 ` Stefan Monnier
2015-08-23 6:33 ` Achim Gratz
2015-08-23 9:17 ` Artur Malabarba
2015-08-23 9:37 ` Achim Gratz
2015-08-23 12:03 ` Artur Malabarba
2015-08-23 22:17 ` Stefan Monnier
2015-08-23 22:12 ` Stefan Monnier
2015-08-23 23:32 ` Artur Malabarba
2015-08-23 22:16 ` Stefan Monnier
2015-08-24 6:56 ` Achim Gratz
2015-08-24 19:17 ` Stefan Monnier
2015-08-24 19:32 ` Achim Gratz
2015-08-24 22:51 ` Artur Malabarba
2015-08-25 5:44 ` Achim Gratz
2015-08-10 14:26 ` Thierry Volpiatto
2015-08-10 15:18 ` Artur Malabarba
2015-08-10 15:38 ` Thierry Volpiatto
2015-08-10 15:53 ` Artur Malabarba
2015-08-10 16:33 ` Thierry Volpiatto
2015-08-10 15:40 ` Nicolas Richard
2015-08-10 15:49 ` Artur Malabarba
2015-08-11 8:44 ` Nicolas Richard
2015-08-11 9:28 ` Artur Malabarba
2015-08-11 9:33 ` Nicolas Richard
2015-08-10 16:34 ` Thierry Volpiatto
2015-08-10 21:49 ` Phillip Lord
2015-08-11 9:24 ` Artur Malabarba
2015-08-10 22:05 ` Stefan Monnier [this message]
2015-08-11 8:56 ` Thierry Volpiatto
2015-08-11 15:55 ` Stefan Monnier
2015-08-10 22:01 ` Stefan Monnier
2015-08-11 9:29 ` Artur Malabarba
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=jwv8u9iiyxu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@gmail.com \
/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.