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

From: Matthew Flatt (mflatt at cs.utah.edu)
Date: Wed Aug 28 07:27:22 EDT 2013

At Wed, 28 Aug 2013 09:45:23 +0200, Konrad Hinsen wrote:
> Lawrence Woodman writes:
> 
>  > I have seen problems with version control crop up for so long and
>  > so often that I can't see why people think Racket and it's
>  > third-party packages would be immune to what has happened in every
>  > other package eco-system I have used: Ruby, Tcl, Shared C Libraries
>  > under Linux, Various Linux Distros, etc.
> 
> +1
> 
> I am all for solving real problems rather than hypothetical ones, but
> I am also for learning from others' mistakes rather than first making
> them myself.

We've had many package-system discussions on the dev mailing list, and
those who are interested or have opinions on the design of the package
system may want to look there.

In particular, see this message from mid-July:

  http://www.mail-archive.com/dev@racket-lang.org/msg09419.html

The section "A Package-Based Racket" is of general interest, and it
will be updated and incorporated into an upcoming blog post.

The section "From Here to There" is obviously out of date. All of that
is done, now.

The "From Back There to Here" section is why I'm citing the post now.
It's a reminder of how we got to the present design, and it's an
attempt to remind everyone that those of us implementing the package
system have had a lot of input over years; we've payed attention and
done our best for this first cut.


Posted on the users mailing list.