Description of problem:

When you run "sepolicy generate" it generates files to define a policy. It also creates <policy_name>.sh file that is supposed to help the user to package the policy module into an RPM package. Unfortunately, in the current state the created script tries to do 2 things at once:

1. install the generated policy into the system
2. package the policy into an RPM package.

While item 1 requires root powers (or more explicitly, administrative rights) to modify the system, item 2 does not require such powers.

It would be nice if the installation and update parts were separated logically inside the created shell script: e.g. if the script is launched with "install" or "update" arguments it will demand root, but if it's executed with "package" - it will simply package the created policy module into an RPM package.

Additional info:

It was also spotted that the auto-generated manual page for the policy module contains a couple of typos:

"other roles need to be transition into" => s/transition/transitioned/
"When using a a non login role," => s/a a non/a non/

Also, the generated manual page contain excessive list of SELinux booleans that are not specifically related to the generated policy module, but to the whole SELinux policy itself. This is redundant and is better to be excluded from a policy module man page (we still have the SEE ALSO list at the end of the page :).