Should fapolicyd be added as a dependency in the tool's rpm spec file?

[tparchambault]

Our favorite tool, fapolicy-analyzer, currently isn't very useful without the existing installation of fapolicyd; Secondarily, the fapolicy-analyzer rpm installation process complains about not being able to communicate with fapolicyd and the nonexistence of /var/lib/fapolicyd/.

My preference would be that fapolicyd is a dependency.

[tparchambault]

For posterity, if fapolicyd is not installed when first running fapolicy-analyzer, one gets the following error after authentication:

ERROR:root:Error initializing System Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/fapolicy_analyzer/ui/features/system_feature.py", line 72, in execute_system system = System() RuntimeError: TrustError(LmdbReadFail(NotFound)) Terminating pkttyagent.

[tparchambault]

As a design decision, the fapolicy-analyzer will have the ability to execute on systems that do not have fapolicyd installed, possibly supporting an off-line use-case where the fapolicy-analyzer tools can analyze data collected from other systems that do have fapolicyd installed.

The above mentioned ERROR has been addressed, with a pop-up dialog providing more information, (currently) followed by termination.