Hi,

While looking into the policy parser from setools v4, we noticed one thing
that is missing: origin of a policy element. For example, given a certain
rule or attribute, it would be great to know in what source file it was
defined.

In Android you can find this information by looking at produced policy.conf
and its comment lines that indicate source file. However I don't know if it
is the same for desktop selinux policy.

Would it be acceptable to have this information as part of python class
representing the parsed policy? It would be really useful for tools like
policy linter, because it would be very much needed to point to the exact
file where some improvements might be desirable.

Best Regards,
Elena.