[Orgmode] Re: Version string (was Re: ELPA Howto)

[Jambunathan K]

Attaching the response from Chong Yidong to my queries. Read down
below.

Jambunathan K.


Carsten Dominik <address@hidden> writes:

> 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.
>

/* Begin Attachment */

From: Chong Yidong <address@hidden>
Subject: Re: Packages + elpa.gnu.org
To: Jambunathan K <address@hidden>
Cc: address@hidden
Date: Fri, 08 Oct 2010 23:55:52 -0400
Message-ID: <address@hidden>

Jambunathan K <address@hidden> writes:

> 1. Who acts as a janitor for the elpa repository.

Me.  Ted Zlatanov also has access.  We've both been pretty busy on other
parts of Emacs lately, though, so there are a couple of packages that
are in the pipeline for uploading (including AuCTEX).

> 2. How does one upload packages - a mail drop to the maintainer, remote
>    update from within emacs - scp, ftp etc etc . (Is package-x.el's
>    package-upload-buffer and related configuration documented
>    somewhere.)

Probably the easiest way to set this up is for someone on the org-mode
team to upload the dailies to a server somewhere on the web, giving the
tarball a deterministic name.  Then, someone (probably me) will have to
set up a cron job on elpa.gnu.org to check for that tarball each day,
download it, and run `package-upload-file' to add it to the repository.

> 3. Does the package manager expect that builtin packages be versioned in
>    a special way. For example, can the stable release be called 7.0.1
>    while a daily snapshot be called 20101008?

The package manager uses the most recent version of a package, as
defined by `version-list-<'.

> 4. Any general guidelines on what packages would be accepted there and
>    how often an update can happen. Are daily snapshots allowed.

The main requirement is for package copyrights to be FSF assigned.  I
think providing dailies is fine.

/* End Attachment */


> 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