From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Strange requirement...
Date: Tue, 25 Jul 2006 09:29:19 +0200 [thread overview]
Message-ID: <85psfujg6o.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1G58JN-0005fq-4L@fencepost.gnu.org> (Richard Stallman's message of "Mon, 24 Jul 2006 17:50:01 -0400")
Richard Stallman <rms@gnu.org> writes:
> This gives, however, no clue about how to deal with declaring versions
> of an external package that is _not_ distributed as part of Emacs
> (notably AUCTeX).
>
> You just follow the instructions for :package-version.
> They seem clear to me. If you don't find them clear,
> could you explain why?
The last sentence of the :package-version description states:
Packages that use the `:package-version' keyword must also update
the `customize-package-emacs-version-alist' variable.
And the immediately following description states:
-- Variable: customize-package-emacs-version-alist
This alist provides a mapping for the versions of Emacs that are
associated with versions of a package listed in the
`:package-version' keyword. Its elements look like this:
(PACKAGE (PVERSION . EVERSION)...)
For each PACKAGE, which is a symbol, there are one or more
elements that contain a package version PVERSION with an
associated Emacs version EVERSION.
But for an external package, there is no associated Emacs version, so
there is no point or sense in updating
`customize-package-emacs-version-alist'.
So I think that the last sentence in the :package-version description
should be something like:
Packages that use the `:package-version' keyword with versions that
have been distributed as part of Emacs must also update the
`customize-package-emacs-version-alist' variable.
For example, the MH-E package updates this alist with the
following:
(add-to-list 'customize-package-emacs-version-alist
'(MH-E ("6.0" . "22.1") ("6.1" . "22.1") ("7.0" . "22.1")
("7.1" . "22.1") ("7.2" . "22.1") ("7.3" . "22.1")
("7.4" . "22.1") ("8.0" . "22.1")))
And the passage before should probably be something like:
`:package-version '(PACKAGE . VERSION)'
This option specifies that the item was first introduced in
PACKAGE version VERSION, or that its default value was changed in
that version. This keyword takes priority over :version. The
value of PACKAGE is a symbol and VERSION is a string. If any
VERSION of PACKAGE has been distributed as part of Emacs, the
combination of PACKAGE and VERSION must appear in the alist
`customize-package-emacs-version-alist'. Since PACKAGE must be
unique and the user might see it in an error message, a good choice
is the official name of the package, such as MH-E or Gnus.
Note that this is just my _guess_ as how to treat this sensibly. I
don't know whether the actual code will complain if it can't find a
given package and version in `customize-package-emacs-version-alist'.
If it does, I think it should likely be changed to match the behavior
I described. But as it stands, the instructions for :package-version
can't be heeded for packages not distributed as part of Emacs.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-07-25 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 6:54 Strange requirement David Kastrup
2006-07-24 21:50 ` Richard Stallman
2006-07-25 7:29 ` David Kastrup [this message]
2006-07-25 22:15 ` Richard Stallman
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=85psfujg6o.fsf@lola.goethe.zz \
--to=dak@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.