6fe2861877
... for the purpose of "populate 'compiled' directories" --- but only if the user has write permission for the package directory. This change may or may not be a good idea. The idea is that installed packages generally should be treated in the same way as the main "collects" tree (e.g., avoiding debugging instrumentation), but if you happen to be developing a package, then you want it treated like things that are not in the main "collects" tree. So, how do you pick? Maybe opening a file in the package is a good way to pick. |
||
|---|---|---|
| .. | ||
| private | ||
| snip | ||
| autosave-recovery-gui.rkt | ||
| easter-egg.rkt | ||
| example-tool.rkt | ||
| follow-log.rkt | ||
| get-defs-test.rkt | ||
| hangman.rkt | ||
| image-and-comment-box.rkt | ||
| incremental-keybindings-test.rkt | ||
| info.rkt | ||
| io.rkt | ||
| language-test.rkt | ||
| memory-log.rkt | ||
| module-lang-test.rkt | ||
| no-write-and-frame-leak.rkt | ||
| online-compilation-zo-creation.rkt | ||
| populate-compiled.rkt | ||
| randomly-click-language-dialog.rkt | ||
| randomly-click-preferences.rkt | ||
| repl-test-debug.rkt | ||
| repl-test-debugprofile.rkt | ||
| repl-test-misc.rkt | ||
| repl-test-raw.rkt | ||
| run.sh | ||
| sample-solutions-one-window.rkt | ||
| sample-solutions-testsuite-tp.scm | ||
| snips.rkt | ||
| stepper-test.rkt | ||
| syncheck-direct.rkt | ||
| syncheck-eval-compile-time.rkt | ||
| syncheck-test.rkt | ||
| teaching-lang-coverage.rkt | ||
| teaching-lang-executable-creation.rkt | ||
| teaching-lang-save-file.rkt | ||
| teaching-lang-sharing-modules.rkt | ||
| teachpack.rkt | ||
| test-docs-complete.rkt | ||
| test-engine-test.rkt | ||
| time-keystrokes.rkt | ||