Ah I see! So is there some heuristic for when you should try to play nice
with Minimal Racket? Is it, ideally, “always”? Or is it mainly if you’re
likely to be using the package on a server, CI, etc?
On Saturday, October 9, 2021 at 1:58:33 PM UTC-5 sorawe...@gmail.com wrote:
> I think it's so t
I think it's so that `raco pkg install mypkg-lib` won't install
`racket-doc` if you use Minimal Racket?
If you don't split `mypkg` to `mypkg-lib` and `mypkg-doc`, but specify
`deps` and `build-deps` correctly, `raco pkg install --binary mypkg` won't
pull in `racket-doc` either. I don't know when t
I’ve always used the single collection format [1] in my packages.
However, I see a lot of package authors will use a multi-collection format
and split the library, documentation and maybe tests out into separate
collections.
What are the benefits of splitting the main library and its documentat
3 matches
Mail list logo
