Version 2.0 planning

[priv-kweihmann]

The current version has way too many limitations, such as the data/valid entries need to be added manually.
For instance if in version x a new item in an Enum appears this cannot be handled by the current implementation.

Version 2.0 is needed.

Proposed features:

• drop support for systemd version prior 2.1x
• extract the supported item set from upstream systemd code (e.g. https://github.com/systemd/systemd/blob/main/man/systemd.unit.xml)
• generate a per release set that inherits the prior ones and only adds new things/changes
• do a mapping of allowed section vs. file ending/path to be more specific (for instance Link section can appear is various files with very different feature sets)
• more support for general configuration files, also for the newly introduced systemd services
• use as a lib
• user/system split see [Security.NoUser] seems a bit harsh for user unit files #64
• EnvironmentFile syntax checks Test content of EnvironmentFile for syntax errors #67

[priv-kweihmann]

We should start using something like https://github.com/wearespindle/versionary to version different variations of the check classes

[dataligand]

Thanks for your work, I was thinking it may be useful to provide a library interface for this project. In my case I'm compiling 'Unit' files for Fedora CoreOS 'ignition' based system (using python) and it would be nice to interact with a lib directly. Again thanks 👏

[priv-kweihmann]

Thanks for your work, I was thinking it may be useful to provide a library interface for this project. In my case I'm compiling 'Unit' files for Fedora CoreOS 'ignition' based system (using python) and it would be nice to interact with a lib directly. Again thanks 👏

That's a good thing to have, I agree - just updated the list of features