Re: Org merging [was Re: next pretest]

[Stefan Monnier]

> If that's your problem then it can be changed easily enough.

That's not the only problem: org-mode is an oddball case nowadays, since
all other packages are "built locally from source".

> The current naming scheme is only in place to provide a continuing
> stream of increasing version numbers to fit in with earlier releases
> of Org as a package.  Changing that would require manual intervention
> from the user to force the "downgrade" of Org once and we wanted to
> avoid that.

I think for the user a version like org-8.2.7.<something>
would be much better than what we have now.

The manual intervention is indeed a problem, but I think we can't really
avoid it (tho package.el should probably be changed to recognize
version numbers of the form 20yymmdd and treat them as "smaller than
they appear").

> I'd still have to check if package.el deals correctly with a package name of
> orgmode-8.2.7c-39-ge112f3c

M-: (version-to-list "8.2.7c-39-ge112f3c")  ==>  error
M-: (version-to-list "8.2.7c.39")  ==>  error
M-: (version-to-list "8.2.7c")  ==>  (8 2 7 3)
M-: (version-to-list "8.2.7.39")  ==>  (8 2 7 39)

So this suggests version numbers shouldn't end in "c", in order to be
able to tack on a "bugfix counter" after it.


        Stefan