Would be worth getting this built into raco

[LeifAndersen]

This seems useful enough a command that it should probably be part of the standard distribution.

[samdphillips]

@samth what do you think needs to happen to add this to the Racket standard distribution?

[LeifAndersen]

Honestly not much. Take a look at raco pkg new:

https://github.com/racket/racket/blob/master/racket/collects/pkg/private/new.rkt

This does basically the same sort of thing.

So a little bit of documentation matching that would do the trick.

[samdphillips]

For my own reference, the link to documentation scribble for pkg subcommands:
https://github.com/racket/racket/blob/master/pkgs/racket-doc/pkg/scribblings/pkg.scrbl#L846

[samth]

How worried should I be about the "experimental" label? How thoroughly tested is this?

In general I definitely want to have this functionality available by default; just want to make sure we don't add it prematurely.

[LeifAndersen]

FWIW I've been using it and its been fine. Two issues:

1. Racket complains if you try to install a package that's already installed in a wider scope. Which is a limitation in Racket.
2. Racket also complains if your current package scope is the same folder as a package you are trying to install. Which also is a limitation/bug with Racket.

I suspect by opening a PR in the main Racket repo there will be other people (cough @mflatt and @jeapostrophe cough) who will have other feedback.

[samdphillips]

How worried should I be about the "experimental" label?

The label is mostly from my uncertainty about the mechanism the tool uses.

[jeapostrophe]

I don't feel like it is that controversial... I think the README/docs don't have enough "why you should care"