[racket] Worried about the new package manager not storing each version of a package

From: Lawrence Woodman (lwoodman at vlifesystems.com)
Date: Sat Aug 31 01:34:48 EDT 2013

On 29/08/13 20:14, Matthew Flatt wrote:
> Package versions are intended to be like semver, but they differ
> syntactically because
>   * the major number should be part of the package name, and
>   * the major number "1" is written "".
> So, write xdgbasedir version 0.1.0 as package name "xdgbasedir0" and
> version "1.0".

Thanks, I was wondering how to signify a package whose api is unstable.
I have renamed the package accordingly.

Maybe the docs should clarify this:

At the moment they only talk about signifying v2 as package2, and hence,
to me, it makes it look as if you should keep it as just the package 
name, until
you are ready to release v2 or above.

It may be a good idea to separate the version number with a hyphen.
So package-2 instead of package2.  The reason I think this would be useful
is if you were providing an interface to another library such as 
libgtk2, you
may decide to completely alter the racket api, but still ultimately use the
libgtk2 library.  So you could go from libgtk2-0 to libgtk2 to 
libgtk2-2, as opposed
to libgtk20 to libgtk2 to libgtk22 which looks strange and has an 
unclear meaning.

Personally I would also be in favour,  if this root were taken, to give 
no special
privilege to the v1 major release and have that hyphenated as libgtk2-1 
as well
for consistency. Especially as I wouldn't be surprised if the minor version
eventually gets tacked on to the package name as a way around the version
problems.  Although this is all repeating information contained in the 
info.rkt anyway.



vLife Systems Ltd
Registered Office: The Meridian, 4 Copthall House, Station Square, Coventry, CV1 2FL
Registered in England and Wales No. 06477649

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20130831/5eeb68db/attachment-0001.html>

Posted on the users mailing list.