Re: ":version" entries in defcustoms

[Miles Bader <miles@gnu.org>]

Simon Josefsson <jas@extundo.com> writes:
>> Adding the custom version later (like I did) is annoying.  How can we
>> simplify this in the future?  The problem is that we don't know the
>> correct Emacs version number (which Emacs will contain this version of
>> Gnus) to add when adding a variable in Gnus.
>
> How about the approach of adding the proper :version cookies when the
> files are integrated into Emacs?  Then you know which version number
> to use (i.e., the next one).  If Gnus developers start to guess next
> non-bugfix Emacs release numbers, things might be more difficult when
> merging Gnus into Emacs in case the guess was wrong.  If there is a
> better way, then that's better, but I don't see it.

I'd suggest adding some sort of unique placeholder when the code gets
originally written, e.g.:

   :version "21.4" ;; rainbow-orangutan

so that later filling in the real version becomes a simple grep (or
tags-query-replace) job.

[The actual value needs to be a real version because
`customize-version-lessp' barfs if you give it anything else]

-Miles
-- 
If you can't beat them, arrange to have them beaten.  [George Carlin]