* Re: [elpa] master 89981d9 1/2: * README: Expand instructions
[not found] ` <E1ZmKWe-0007S7-FX@vcs.savannah.gnu.org>
@ 2015-10-14 13:24 ` Stefan Monnier
2015-10-14 14:05 ` Artur Malabarba
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Monnier @ 2015-10-14 13:24 UTC (permalink / raw)
To: emacs-devel; +Cc: Artur Malabarba
> -The file needs to follow the usual coding conventions (most importantly
> -start with ";;; <file> --- <description>") and have a "Version:" and
> -"Maintainer:" pseudo-header.
> +The file needs to follow the usual coding conventions (most
> +importantly start with ";;; <file> --- <description>") as well as the
> +package headers required by package.el (see the "Format" subsection
> +below).
I think this isn't quite right:
- package.el does not require any package headers in general, whereas we
always require them, even for multi-file packages (because we always
auto-generate the *-pkg.el file).
- AFAIK package.el does not require (or even pay attention to)
a "Maintainer:" header, but we do.
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [elpa] master 89981d9 1/2: * README: Expand instructions
2015-10-14 13:24 ` [elpa] master 89981d9 1/2: * README: Expand instructions Stefan Monnier
@ 2015-10-14 14:05 ` Artur Malabarba
2015-10-14 15:53 ` Stefan Monnier
0 siblings, 1 reply; 3+ messages in thread
From: Artur Malabarba @ 2015-10-14 14:05 UTC (permalink / raw)
To: Stefan Monnier; +Cc: emacs-devel
I'll change that back.
BTW, since (lm-maintainer) uses the author as a fallback, am I correct
to assume that Elpa does the same?
2015-10-14 14:24 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> -The file needs to follow the usual coding conventions (most importantly
>> -start with ";;; <file> --- <description>") and have a "Version:" and
>> -"Maintainer:" pseudo-header.
>> +The file needs to follow the usual coding conventions (most
>> +importantly start with ";;; <file> --- <description>") as well as the
>> +package headers required by package.el (see the "Format" subsection
>> +below).
>
> I think this isn't quite right:
> - package.el does not require any package headers in general, whereas we
> always require them, even for multi-file packages (because we always
> auto-generate the *-pkg.el file).
> - AFAIK package.el does not require (or even pay attention to)
> a "Maintainer:" header, but we do.
>
>
> Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-10-14 15:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20151014114716.28563.42497@vcs.savannah.gnu.org>
[not found] ` <E1ZmKWe-0007S7-FX@vcs.savannah.gnu.org>
2015-10-14 13:24 ` [elpa] master 89981d9 1/2: * README: Expand instructions Stefan Monnier
2015-10-14 14:05 ` Artur Malabarba
2015-10-14 15:53 ` Stefan Monnier
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.