> I think you're right. My application is the replacement tool for McFly, and > I want to eliminate the need for distributed packages to need a package > dependency like on `mcfly-runtime`.
Maybe you don't need to eliminate that? It would only be a build dependency: A using package's info.rkt would list your package in `build-deps` not `deps`. Although your package would still get installed for developers who don't use it directly, at least it would be omitted from binary packages: http://docs.racket-lang.org/pkg/strip.html -- 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.
