Bastiaan Veelo

If the introduction of `$SOURCE_PACKAGE_PATH` makes anything easier, I would be happy with that. At least it gives me a way out of #2229, so I can move on.

> > Right now a workaround to add a dummy "library" package that's just there to run commands should work as well, if we decide to keep this behavior. >...

> In the meantime, @veelo did using `$_PACKAGE_DIR` solve your blocker? Thank you for this suggestion, that might work. I changed it into a dummy (ordinary) library a while ago,...

This PR has been merged as part of #8995 .

The same happens on Windows.

The `shared` cheats have been moved into the logger implementation by Átila, so that user code can follow proper shared practices, which is now documented. I noted that `stable` has...

@CyberShadow from #1823: > JSON has proven to be a bad format for human-written configuration. Be it the lack of comments, noisy syntax, lack of typing... So much that a...

Thank you @Geod24. I am struggling a bit with `test\issue1651-custom-dub-init-type`, which is failing on macOS and ubuntu. I am running Windows locally. That particular test only contains a .zip file,...

Got it. To reproduce on Windows: ``` cd test\issue1651-custom-dub-init-type %DUB% remove custom-dub-init-dubpackage --non-interactive %DUB% init -n custom-dub-init-type-sample --format sdl -t custom-dub-init-dubpackage --skip-registry=all --registry=file://D:\SARC\dlang\dub\test\issue1651-custom-dub-init-type -- --foo=bar ```

> Though it looks like `run-unittest.d` is skipping `.sh` tests on windows unconditionally, maybe making it run them if `bash` is found in `PATH` is a better idea Even better...