Dominique Dumont

There also a workaround for nested bullet list. White space can be inserted with Go template: ``` - item {{ " " }} - nested item - item ``` HTH

I have a similar behavior when packaging JSON::Fast for Debian. On the other hand, I've no problem with JSON::Marshall

Yes. Here's the output of install-dist.raku with raku 2022.07 : ``` $ rm -r /tmp/raku-test/ $ raku --version Welcome to Rakudo™ v2022.07. Implementing the Raku® Programming Language v6.d. Built on...

I think that, when building a package, the build process should: - not use `$HOME/.precomp` at all - use only precompiled files from CORE when building for vendor (as indicated...

> The upshot is that adding something like RAKULIB="inst#/usr/lib/perl6/vendor,$RAKULIB" to the install-dist.raku" command should avoid the precomp issue you showed. Indeed, `$HOME/.raku/precomp` is not longer used, but, unfortunately, the precomp...

On a hunch, I've set `RAKULIB` to the target directory. Now, precompiled files can be found in target directory: ``` $ export RAKULIB="inst#/tmp/raku-test" $ raku /usr/share/perl6/tools/install-dist.raku --to=/tmp/raku-test --for=vendor --from=. 1...

> I need to check if JSON::Marshal can find its dependencies when JSON::Fast is installed in vendor dir, i.e. when installed as a Debian package. Looks like it's working fine....

> So that script seems to work just fine as always and the bug indeed seems to be in install-dist.raku. On my side, I've not seen much difference between install-dist.raku...

> Are you by any chance building JSON::OptIn in an environment that has JSON::Name (or some other reverse-dependency of JSON::OptIn) already installed and in the vendor Rakudo installation? No. Without...

Looks like rakudo insists on creating `$HOME/.raku/short` directory even though this path is not in `$RAKUDOLIB`. (See [Debian bug 1020788](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020788) for details and some logs). This is inconvenient but easy...