Consider vendoring various dlang-community tools
Currently, it looks like we'll need (some variant of) ddoc
along with D-scanner
for linting, dfmt
for enforcing default dlang .editorconfig
style settings and possibly dfix
for future automatic upgrades of the code-base to newer Dlang upstream versions (automatically fixes deprecated syntax etc.).
With the recent switch to the meson
build tool, it might make sense to keep a single serpent-style/
dir alongside the tool clones and then vendor in the above tools as submodules for use in linting and doc creation via dedicated serpent-style/scripts/
artefacts symlinked into each Serpent OS tooling project.
Benefits:
- Less space required
- Single-source currently checked out
serpent-style/
version (and submodules) for linting etc. updates - Changes/updates to
serpent-style
automatically reflected across relevant Serpent OS tooling code bases (via symlinks)
Drawbacks:
- None that I can think of?
Comments welcome.
Edited by Rune Morling