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

[snip]
Sorry, when I said multiple Racket applications, I meant multiple
applications written in racket.  E.g  If I had a web scraper/site monitor
running constantly as well as a music manager.  They both use a html
package, but need different versions of this package. Having multiple
installations of Racket would certainly be an option, but what a horrible
one.
[/snip]

Actually, with

1. The movement towards a minimal Racket installation, and
2. Movement of many things into the package system

having a small Racket install for different projects won't be a big deal.
And, you've just suggested two projects that are, essentially, "production"
services. I wouldn't run a production service on a constantly changing
base. I would want my language and packages to remain constant, and I would
only do upgrades of either when I knew there was a good reason (security
updates, features) that required me to do so. If it's a cutting edge
"production" service, then I'm expecting to constantly upgrade everything,
and the idea that I would freeze something seems counterintuitive.

So, all of this doesn't bother me at all. For a long time, I had tools that
did not migrate from... er, possibly v4xx to v5xx?... because they "just
worked." They had a known lifetime, and it didn't matter to me that the
Racket world had moved on. Some of them ultimately upgraded, some didn't.

Like Matthew said, the tools continuously improve. If it turns out the new
package manager has obvious space for improvement in practice, the core
team and community will, no doubt, address it.

Cheers,
Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20130827/3e20314d/attachment.html>