On Tue, Nov 12, 2019 at 2:09 PM Matthew Flatt <mfl...@cs.utah.edu> wrote: > > I'd say the problem is that "info.rkt" and `find-relevant-directories` > are set up as Racket-installation concepts. They're not made to play > well with standalone applications. > > The most similar concept that plays well with standard applications is > libraries in the Racket "lib" directory. Having packages that supply > timezone information install the timezone files to Racket's "lib" (in > the same way that a package like "db-win32-x86_64" installs a library) > might be a better approach in the long run. > > If I understand, these files would make more sense in a "share" > directory than in the "lib" directory. If that distinction seems > important, we could add a 'share mode to `define-runtime-path` that is > similar to 'lib mode. > > > I think your solution so far, which relies on compile-time checks, will > not work right with packages that are distributed in "built" form. That > creates a problem, in turn, for building a Racket distribution. >
I hadn't thought of built packages, but, yes, that sounds like a problem. I like the idea of installing the data to a "share" directory. I see that the `info.rkt` file for a collection has a `copy-shared-files` key. In my case, both the `tzinfo` package and the `tzdata` package contribute to the `tzinfo` collection. So, two questions: (1) Would it work just to add this to the collection-level `info.rkt` in the `tzdata` package? (2) How do I locate these files after they're copied? Is this what the (notional) 'share mode for `define-runtime-path` would do? - Jon -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAKfDxxz%3D6H1X0hTSXczu9_PeLEhr_JrOC4QdJJYhkBPFJ0ybTQ%40mail.gmail.com.
