From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: Customize :package-version keyword
Date: Sat, 22 Apr 2006 02:14:33 +0200 [thread overview]
Message-ID: <m3fyk6wjo6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <3518.1145405408@olgas.newt.com>
Bill Wohler <wohler@newt.com> writes:
> The :version keyword (used in defcustom, defgroup, and defface) isn't
> very helpful for packages such as MH-E (and probably Gnus as well) which
> have releases more often than Emacs. For example, MH-E has had two major
> releases and a score of minor releases.
I'm a bit fuzzy on what :version is trying to achieve. Are users
supposed to list new options that have arrived since some other
version? And have any users ever done this? :-)
> After broaching this subject on emacs-devel
> (http://article.gmane.org/gmane.emacs.devel/51453), I ended up
> implementing :package-version using ideas provided by Richard. If you
> add, for example,
>
> :package-version '(MH-E . "8.0")
Makes sense to me, I think. On the other hand, I've always considered
the version of Gnus included with Emacs/XEmacs the "real" version,
on the vague idea that most Gnus users uses the pre-packaged version
of Gnus. (I have no data that supports this notion. :-)
So I'm not quite sure I feel that this level of detailed user-visible
versioning is required...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2006-04-22 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 0:10 Bill Wohler
2006-04-22 0:14 ` Lars Magne Ingebrigtsen [this message]
2006-04-22 1:16 ` Bill Wohler
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=m3fyk6wjo6.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).