On Tue, Sep 1, 2015 at 2:23 PM, Jack Firth <jackhfi...@gmail.com> wrote: > In order to support this, would it make sense for the package X to have > something like this in it's info.rkt? > > (define version-sources > (hash "1.0" package-source-for-foo-1.0 > "1.1" package-source-for-foo-1.1 > "2.0" package-source-for-foo-2.0)) > > I think it would be possible for the package catalog and package build > server to use this information to figure out what to do with requests for a > particular version of a package name. I don't know enough about the > implementation of that infrastructure to know how feasible this is however.
This is an interesting idea and I'd be curious how a patch that implemented it would look. One thing that would be difficult, I expect, is that presently packages never mention their own sources or the sources of other packages, typically. This facilitates new implementations of the same interfaces and controlling what code you have installed by freezing an old catalog. I think what you really might want is another tool for building a catalog. If you are currently happy with a release of a package you have, you can freeze the checksum and get the same checkout on another computer, rather than reinstalling and getting the latest release. It's conceivable that the package info lookup API with the catalog could include "I want version X", but because new versions are defined to be backwards compatible, as long as the server has some version that's after X, then there is no reason to know what any old version has, since any client should be happy with any release >X. Jay -- Jay McCarthy http://jeapostrophe.github.io "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33 -- 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 racket-dev+unsubscr...@googlegroups.com. To post to this group, send email to racket-dev@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAJYbDanwYAR7bSyRhfKbgrvV%2BpHgNHFzR%3D_FCuJKMuunrXueYw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
