From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: Version string (was Re: ELPA Howto) Date: Fri, 08 Oct 2010 20:56:58 +0530 Message-ID: <81lj68wvc4.fsf@gmail.com> References: <81pqvvofgz.fsf@gmail.com> <814od06gls.fsf_-_@gmail.com> <13824DEB-A43A-4E87-A5DD-84C5965C713C@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=53198 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P4F1B-0005lT-Ee for emacs-orgmode@gnu.org; Fri, 08 Oct 2010 11:37:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P4F1A-0005yp-78 for emacs-orgmode@gnu.org; Fri, 08 Oct 2010 11:37:57 -0400 Received: from mail-px0-f169.google.com ([209.85.212.169]:55259) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P4F1A-0005xt-2K for emacs-orgmode@gnu.org; Fri, 08 Oct 2010 11:37:56 -0400 Received: by pxi5 with SMTP id 5so64341pxi.0 for ; Fri, 08 Oct 2010 08:37:53 -0700 (PDT) In-Reply-To: <13824DEB-A43A-4E87-A5DD-84C5965C713C@gmail.com> (Carsten Dominik's message of "Fri, 8 Oct 2010 12:38:43 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org (Resent to mailing-list) Carsten Dominik writes: > On Oct 5, 2010, at 1:09 PM, Jambunathan K wrote: > >> >> In the context of ELPA packages, I think there might be a need to >> revisit how orgmode's version string is defined. >> >> For example, 7.01h wouldn't be successfully parsed by (version-to-list >> ...) which the package manager uses internally. >> >> So 7.01h could be mapped to 7.0.1.8 or 7.1.8. > > > Hi Jambunthan, > > in what places would the version string have to be modified? > Do I need to change the org.el variable org-version, or the string in > the VERSION keyword in file headers, or where? > >From a functional perspective, there is *no need* to modify any of the el files. One has to just take care that PKG_TAG is a 'version-to-list'-compatible string. The tarball thus generated will be very much usable. >From a maintenance perspective you might want to move away from 7.01h convention and adopt a convention that is dictated by elpa. Jambunathan K. > - Carsten > >> >> ,----[ C-h f version-to-list RET ] >> | version-to-list is a compiled Lisp function in `subr.el'. >> | >> | (version-to-list VER) >> | >> | Convert version string VER into an integer list. >> | >> | The version syntax is given by the following EBNF: >> | >> | VERSION ::= NUMBER ( SEPARATOR NUMBER )*. >> | >> | NUMBER ::= (0|1|2|3|4|5|6|7|8|9)+. >> | >> | SEPARATOR ::= `version-separator' (which see) >> | | `version-regexp-alist' (which see). >> | >> | The NUMBER part is optional if SEPARATOR is a match for an element >> | in `version-regexp-alist'. >> | >> | As an example of valid version syntax: >> | >> | 1.0pre2 1.0.7.5 22.8beta3 0.9alpha1 6.9.30Beta >> | >> | As an example of invalid version syntax: >> | >> | 1.0prepre2 1.0..7.5 22.8X3 alpha3.2 .5 >> | >> | As an example of version convertion: >> | >> | String Version Integer List Version >> | "1.0.7.5" (1 0 7 5) >> | "1.0pre2" (1 0 -1 2) >> | "1.0PRE2" (1 0 -1 2) >> | "22.8beta3" (22 8 -2 3) >> | "22.8Beta3" (22 8 -2 3) >> | "0.9alpha1" (0 9 -3 1) >> | "0.9AlphA1" (0 9 -3 1) >> | "0.9alpha" (0 9 -3) >> | >> | See documentation for `version-separator' and `version-regexp- >> alist'. >> | >> | [back] >> `---- >> >> Jambunathan K. > > - Carsten