Philip McGrath

> > Racket as a project is of course willing to make a statement of license compliance, and state what licenses apply, for the code that it distributes. > >...

That all makes sense to me, and I don't have a strong view myself (especially given that my interest is primarily in Racket). Actually, I think these results are ultimately...

It might be worth looking at other language/library APIs for json pretty-printing. For example, Python's [`json.dump`](https://docs.python.org/3/library/json.html?highlight=json#json.dump) (not always a model to emulate!) says: > If *indent* is a non-negative integer...

> From what I understand, it is not well defined what is native code for linklets and what is pure Racket. I think this depends on what you mean by...

I've rebased, since https://github.com/racket/racket/pull/3870 was merged, but I haven't tackled the test failures of other issues. > So far, I don't think `copy-file `should have a permissions argument. It seems...

I was reminded by https://github.com/racket/racket/issues/4357 of the idea of `#:permissions` for `copy-file`, though I don't think it has persuaded me that it would really be a good idea.

> I don't think I have ever mutated a string except to demonstrate bugs caused by the mutability of strings. Here's one of those "bugs caused by the mutability of...

Thanks for the ideas! They led me to at least one problem—the `lib-search-dirs` were being duplicated, including ancestor layers and `#f` multiple times—but fixing that hasn't resolved the overall problem....

With further experimentation, it appears it is indeed the final `raco pkg install` step that somehow rewrites the `racket` binary incorrectly. I'll try to reproduce more minimally.

The example at https://github.com/racket/racket/issues/4133 now (as of commit cbf1bed) reproduces the issue without Guix. Just adding launcher with `racket-launcher-{names,libraries}` wasn't enough, but installing in a layer a package that depends...