From: Jambunathan K <kjambunathan@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Version string (was Re: ELPA Howto)
Date: Sat, 09 Oct 2010 10:57:30 +0530 [thread overview]
Message-ID: <8139sgx7el.fsf@gmail.com> (raw)
In-Reply-To: <B6407937-5D3E-4551-86E7-98752A89D493@gmail.com> (Carsten Dominik's message of "Fri, 8 Oct 2010 13:45:43 +0200")
Attaching the response from Chong Yidong to my queries. Read down
below.
Jambunathan K.
Carsten Dominik <carsten.dominik@gmail.com> 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 <cyd@stupidchicken.com>
Subject: Re: Packages + elpa.gnu.org
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-devel@gnu.org
Date: Fri, 08 Oct 2010 23:55:52 -0400
Message-ID: <87y6a86muv.fsf@stupidchicken.com>
Jambunathan K <kjambunathan@gmail.com> 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
next prev parent reply other threads:[~2010-10-09 5:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 7:30 ELPA Howto Jambunathan K
2010-09-30 14:34 ` Jeff Horn
2010-10-02 18:22 ` Eric Schulte
2010-10-03 4:23 ` Jambunathan K
2010-10-04 1:28 ` Eric Schulte
2010-10-04 13:15 ` Eric Schulte
2010-10-20 16:37 ` Bastien
2010-10-20 19:44 ` Jambunathan K
2010-10-20 21:00 ` Eric Schulte
2010-10-04 13:39 ` Carsten Dominik
2010-10-04 17:29 ` Jambunathan K
2010-10-04 18:23 ` Jambunathan K
2010-10-05 2:13 ` Carsten Dominik
2010-10-05 10:11 ` Jambunathan K
2010-10-05 11:09 ` Version string (was Re: ELPA Howto) Jambunathan K
2010-10-08 10:38 ` Carsten Dominik
2010-10-08 11:45 ` Carsten Dominik
2010-10-09 5:27 ` Jambunathan K [this message]
2010-10-08 15:26 ` Jambunathan K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8139sgx7el.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).