Ideas for packaging rule sets?

[bollwyvl]

vale doesn't do anything out-of-the-box, and seems to lean towards downloading to a relative path, per project, from... wherever after discovering them on https://vale.sh/hub/

It will apparently discover hunspell dictionaries in the well-known location, which is probably worth taking a look at.

Some related upstream issues:

• default StylesPath errata-ai/vale#295
• Feature: Support environment variable for vale.ini location errata-ai/vale#576

Next Steps:

• investigate this after vale v3.0.0 #17
• start packaging
  • first-party packages
    • Add vale-styles-*  staged-recipes#25017
  • spelling
    • hunspell en-*
      • Add vale-spelling-*-en-dict staged-recipes#25038
  • third-party
    • redhat?
      • Update Vale at Red Hat for Vale 3.0.0 redhat-documentation/vale-at-red-hat#704
    • mailchimp?
      • https://github.com/testthedocs/MailChimp
    • others?
      • https://github.com/search?q=vale_version+path%3Ameta.json&type=code

[bollwyvl]

Haven't yet tried this is anger, but am leaning towards a setup that would fiat ${PREFIX}/share/vale (as suggested on an upstream) issue, then have some out-of-band mechanism (make, doit, etc.) symlink (or copy) them to some per-project location.

Still not sure how to make this work properly with e.g. hunspell-en, due to the singleton StylesPath, as it seems there's no way to have some things be relative to a style path, and others be relative to the config file location. More copying, I guess.