I don't understand this question. The package system doesn't really have a
concept of version like you are referring to.
The package X is versionless. It is possible to know that your copy of X is
different than another's, hence checksums and updating (which should have
been called sync, in retros
Although I object to some of your characterizations of the difference
between PLaneT and the new package system, it's fair to say that PLaneT
provides better support to package authors for creating new APIs that
are intended to replace (but coexist with) old APIs.
I think the answer to that proble
Any chance of revisiting the new package system's stances on versions --
specifically, on the two issues:
1. Can subsequent versions of a named package (which has an identity)
be non-backward-compatible?
2. Can a Racket setup (and even an individual program) have multiple
versions of a package
3 matches
Mail list logo
