emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [CONCERN] Orgmode version string
Date: Fri, 29 Oct 2010 18:36:23 +0530	[thread overview]
Message-ID: <811v79f8s0.fsf@gmail.com> (raw)
In-Reply-To: <E35B68D7-33D9-4BF2-B3E2-A81678A0C782@gmail.com> (Carsten Dominik's message of "Thu, 28 Oct 2010 23:57:46 +0200")


Carsten

> Hi Jambunathan,
>
> On Oct 28, 2010, at 2:40 PM, Jambunathan K wrote:
>
>>
>> I have every reason to believe that upcoming version of Org would be
>> tagged as 7.02. Earlier I had argued that version strings be
>> version-to-list compatible. I would like to reiterate it.
>>
>> My real concern is that 7.02 would be deemed as equivalent to 7.2
>> internally by the versioning subsystem and this is likely to clash
>> with
>> user's point of view. A user would *definitely* assume 7.02 as
>> different
>> from 7.2 and in all probability swear that former is inferior to the
>> later.
>
> (version-to-list "7.02")  -> (7 2)
> (version-to-list "7.20")  -> (7 20)
>
> so it seems to me that if we keep two-digit numbers, there will be no
> problem at all.
>
> #+begin_src emacs-lisp
>  (version-list-= (version-to-list "7.02") (version-to-list "7.20"))
> #+end_src
>
> - Carsten
>

Now that release-7.02 is out, I am a bit disappointed that a ELPA-tar
named org-7.02.tar would be unusable.

The reason is "7.02" doesn't round-trip well and package manager is
allergic to such a choice. Verify this for yourself.

#+begin_src emacs-lisp
 (package-version-join (version-to-list "7.02"))
#+end_src

If you don't mind sharing, I am curious what made you still go with 7.02
scheme.

Jambunathan K.

>>
>> Please confirm what I am saying by evalling this:
>>
>> #+begin_src emacs-lisp
>>  (version-list-= (version-to-list "7.02") (version-to-list "7.2"))
>> #+end_src
>>
>> Ignore this mail if it is already taken care of. Needless to say, I
>> have
>> ELPA-tarballs in mind when I say this.
>>
>> Jambunathan K.
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  parent reply	other threads:[~2010-10-29 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 12:40 [CONCERN] Orgmode version string Jambunathan K
2010-10-28 14:06 ` Bastien
2010-10-28 16:27   ` Jambunathan K
2010-10-28 18:16   ` Jambunathan K
2010-10-28 21:57 ` Carsten Dominik
2010-10-29  1:36   ` Jambunathan K
2010-10-29 13:06   ` Jambunathan K [this message]
2010-10-29 14:51     ` Carsten Dominik
2010-10-29 17:53       ` Jambunathan K
2010-10-29 14:53     ` Bastien

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=811v79f8s0.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).