The things you notice in distro QA... With s subdir of d/allocator, projects will search for stdx.allocator in /usr/include/d/allocator/, which doesn't exist. The module is in /usr/include/d/stdx/stdx/allocator (double-stdx as always, because /usr/include/d/ is in many D compiler's default include path which sometimes leads to the compiler including unwanted (system) copies of a module - which is a real nightmare in case the modules contain templates and you are debugging it and wonder why changes you make have no effect).
Therefore, the right subdir string is d/stdx/.
This PR also updates the project version number and sets a slightly more descriptive package summary for pkg-config.
(since a CI pass is required, I can't push the minor changes like a version update to master directly, unfortunately)
The things you notice in distro QA... With s
subdir
ofd/allocator
, projects will search for stdx.allocator in/usr/include/d/allocator/
, which doesn't exist. The module is in/usr/include/d/stdx/stdx/allocator
(double-stdx as always, because/usr/include/d/
is in many D compiler's default include path which sometimes leads to the compiler including unwanted (system) copies of a module - which is a real nightmare in case the modules contain templates and you are debugging it and wonder why changes you make have no effect). Therefore, the right subdir string isd/stdx/
.This PR also updates the project version number and sets a slightly more descriptive package summary for pkg-config. (since a CI pass is required, I can't push the minor changes like a version update to master directly, unfortunately)