> > To do that, you can put the package source for the specific version > (instead of the name) in the deps specification, and if the package isn't > already installed, it goes to that package source instead of through the > catalog. That doesn't work if the user already has the newer version > installed though, because it would just assume the newer version will work. >
That seems like it could do as a workaround, but handling versioning shouldn't require going around the package catalog completely. -- 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/870ebf85-f6e0-485d-81b6-367e877f48e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
