This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Question about clisp version naming
- From: Yaakov Selkowitz <yselkowitz at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 11 Mar 2015 17:20:33 -0500
- Subject: Re: Question about clisp version naming
- Authentication-results: sourceware.org; auth=none
- References: <5500B536 dot 4050108 at cornell dot edu>
On Wed, 2015-03-11 at 17:35 -0400, Ken Brown wrote:
> I've succeeded in making dynamic loading of modules work in clisp on
> Cygwin, and I'll be issuing a new release soon.
Yeah!
> My work was based on the tip of the upstream Mercurial repository, which
> shows a version number of 2.49+ and is at revision 15623. So I was
> thinking of using 2.49+hg15623 as the version number. Will upset be
> happy with that? Or is there some other standard way of assigning
> version numbers in cases like this?
With setup now being stricter about versions wrt upgrading, we need to
be as well. Because this is a post-2.49 revision, it should be
VERSION=2.49 and RELEASE=2.YYYYMMDDhg15623 (since there was already a
-1).
--
Yaakov