Any ideas for ensuring that all "released versions" of non-core Racket
packages in the new package system remain accessible (short-term, and
long-term)?
Ideas other than the current ad-hoc people individually
copying&preserving the versions that they use or anticipate someday
using (which, incidentally, tends to result in lazy copy&paste&modify,
rather than shared reusable components).
And, ideas other than "just use github". (Though one could make some
pragmatic arguments for that, but I'm interested in alternatives.)
One idea is for the "packages.racket-lang.org" server to double as a
server of all current and past versions of packages, like was done for
PLaneT.
Neil V.
--
You received this message because you are subscribed to the Google Groups "Racket
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/56636C4B.3030909%40neilvandyke.org.
For more options, visit https://groups.google.com/d/optout.
