Re: defcustom :version

[Bill Wohler <wohler@newt.com>]

Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> On Sat, Mar 11 2006, Bill Wohler wrote:
> 
> > We don't use any :version keywords in the MH-E package at the moment,
> > although I'd like to add them. Before doing so, I hope you can help me
> > answer a couple of questions about them.
> >
> > First, how are people using the defcustom :version keyword?
> 
> Maybe you already know this but... you don't need to add the keyword
> to each variable: You can also add it to the custom group. 

Yup, I did.

> Not really an answer to the questions you raised, but this is how I
> suggest to handle it in Gnus:
> 
> ,----[ (info "(gnus-coding)Gnus Maintainance Guide") ]
> | For new customizable variables introduced in Oort Gnus (including the
> | v5-10 branch) use `:version "22.1" ;; Oort Gnus' including the comment.
> | If the variable is new in No Gnus use `:version "23.0" ;; No Gnus'.
> `----

Good idea. That way you'll at least have the information available until
it can be incorporated. I'll do that for now.

> > Unless, of course, folks think is reasonable and proper that large
> > independent packages that happen to be bundled with Emacs can use their
> > versions with the defcustom :version keyword.
> 
> This only would make sense if `customize-changed-options' could handle
> such "package versions".  Maybe extending the format to allow plists
> such as...
> 
>   :version '(:emacs 22.1 :mh-e 7.0)
>   :version '(:emacs 22.1 :gnus 5.10.2)

Good. That would actually be more general than the solution I proposed.

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.