Hi Robby, On Sunday, February 18, 2018 at 10:33:09 AM UTC+8, Robby Findler wrote: > > FWIW, the approach that is less friendly to your clients but perhaps > easier for you (and maybe good enough for them) is to declare a > dependency on a specific version in the info.rkt file of your pkg. The > pkg system will ensure that the latest version is used. >
I have an application, not a package, so there is no "info.rkt" file in which to declare dependencies. I do not use any external packages or features specific to a Racket version, so I did not need any version management of the libraries I use. This is the first case where I need something that is not present in all racket versions -- in fact,currently, it is only present in an unreleased version. The suggested `dynamic-require` approach seems simple enough and it is probably more user (developer) friendly. It also has the benefit that I understand how it works :-) Best Regards, Alex. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
