From: Jambunathan K <kjambunathan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bastien <bzg@gnu.org>, Stromeko@nexgo.de, emacs-devel@gnu.org
Subject: Re: Version strings in lisp files?
Date: Sat, 21 Apr 2012 20:04:41 +0530 [thread overview]
Message-ID: <81pqb1m9vi.fsf@gmail.com> (raw)
In-Reply-To: <83mx65goj2.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Apr 2012 17:14:41 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> AFAIK, the policy is that _if_ you want some version string in a
> package, then keep that to a minimum (1 file). But there's no policy,
> AFAIK, to have a version string, if Org doesn't need that.
Leaving aside question of Org,
,---- from package.el
| ;; Prefer Package-Version; if defined, the package author
| ;; probably wants us to use it. Otherwise try Version.
| (pkg-version
| (or (package-strip-rcs-id (lm-header "package-version"))
| (package-strip-rcs-id (lm-header "version"))))
`----
,---- from package.el
| (unless pkg-version
| (error
| "Package lacks a \"Version\" or \"Package-Version\" header"))
`----
I think the policy differs based on what elisp file is being
considered....
The above data point is inconsequential for non-core Org because it is a
multi-file package and it's version comes from `org-pkg.el' bundled
within the tar.
--
next prev parent reply other threads:[~2012-04-21 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:27 Version strings in lisp files? Achim Gratz
2012-04-21 12:37 ` Jambunathan K
2012-04-21 13:19 ` Bastien
2012-04-21 14:09 ` Jambunathan K
2012-04-21 14:28 ` Bastien
2012-04-21 13:43 ` Eli Zaretskii
2012-04-21 14:11 ` Bastien
2012-04-21 14:14 ` Eli Zaretskii
2012-04-21 14:34 ` Jambunathan K [this message]
2012-04-21 14:48 ` Eli Zaretskii
2012-04-21 14:47 ` Achim Gratz
2012-04-21 19:40 ` Stefan Monnier
2012-04-21 19:54 ` Achim Gratz
2012-04-21 22:59 ` Bastien
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=81pqb1m9vi.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=bzg@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.