I would recommend adding `info.rkt` files to your projects so that your projects are *themselves* packages. In these info files you can declare what packages you depend on, so rather than manually installing dependencies one at a time globally (and reinstalling when upgrading racket), you simply install your project as a package and `raco pkg` will fetch all the dependencies you listed.
If you're writing things that tend to be one-off scripts rather than full-blown projects and the overhead of an `info.rkt` file irks you, have a look at Scripty[1]. This is a Racket package that lets you write scripts that declare what packages they depend on in the script itself -- when you run the script, it prompts you to install any declared packages that aren't present. It's especially useful for replacing random shell scripts with racket scripts without forcing your coworkers to confront the racket packaging system. [1] http://docs.racket-lang.org/scripty/index.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.
