Bastiaan Veelo

I have been using `$PACKAGE_DIR` in places where I should have been using the other variables, but I didn't because I couldn't get them to work, due to the bug...

> I will investigate today whether I can work without `$PACKAGE_DIR` in those commands I don't think I can. If you have commands in a `sourceLibrary` (which obviously is a...

Understood. Variables are quite flaky. Dub 1.27.0 also has the issue that for a `tagetType none` package with a sub-package on which it depends, both having `preGenerateCommands`, the `$PACKAGE_DIR` in...

Since #2217 made it into [D 2.100.0](https://dlang.org/changelog/2.100.0.html#command-variables), this has turned into a blocker for us, meaning we are stuck at 2.099 :-( If this issue cannot be resolved, and https://github.com/dlang/dub-docs/pull/26...

Note that I am not alone in using `$PACKAGE_DIR` inside `preGenerateCommands`, here is another example: #2238. In fact I think this is the primary use case for `$PACKAGE_DIR` (because the...

> the variables work, just not under `sourceLibrary` target type. Then https://github.com/dlang/dub-docs/pull/26 should be reverted, no?

I would really appreciate if this regression can be fixed before the next release. It is holding us back from compiler upgrades.

Thank you for investigating the cause of the problem, @Moth-Tolias!

Are you sure it does a full rebuild every time? On second invocation I "only" get: ``` Running pre-generate commands for dscanner... Performing "debug" build using C:\D\dmd2\windows\bin\dmd.exe for x86_64. stdx-allocator...

Curious indeed. I have a project where I call `dub run dfmt` repeatedly, and it recompiles every time as well, like you have with `dscanner`.