From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Version string (was Re: ELPA Howto) Date: Fri, 8 Oct 2010 13:45:43 +0200 Message-ID: References: <81pqvvofgz.fsf@gmail.com> <814od06gls.fsf_-_@gmail.com> <13824DEB-A43A-4E87-A5DD-84C5965C713C@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=50949 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P4BOZ-0003Iv-J5 for emacs-orgmode@gnu.org; Fri, 08 Oct 2010 07:45:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P4BOX-0006xR-Vc for emacs-orgmode@gnu.org; Fri, 08 Oct 2010 07:45:51 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:47515) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P4BOX-0006xH-Nk for emacs-orgmode@gnu.org; Fri, 08 Oct 2010 07:45:49 -0400 Received: by ewy4 with SMTP id 4so537899ewy.0 for ; Fri, 08 Oct 2010 04:45:48 -0700 (PDT) In-Reply-To: <13824DEB-A43A-4E87-A5DD-84C5965C713C@gmail.com> 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: Carsten Dominik Cc: emacs-orgmode@gnu.org, Jambunathan K Hi, so how do we move forward with generating packages? I have installed the code by Jambunthan in the Make file, but I guess we still need to negotiate with the EPLA on how to upload and update the package, about name conventions etc. Is there anyone whole is willing to sort this all out and then show us the simple upload recipe? My feeling is that the latest release should be on the package server. daily bleeding edge builds could be there as well, under a different name. Thanks - Carsten On Oct 8, 2010, at 12:38 PM, Carsten Dominik wrote: > > 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? > > - 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 > > > - Carsten