https://bugzilla.redhat.com/show_bug.cgi?id=2252811
--- Comment #8 from Paul Pfeister <rh-bugzilla(a)pfeister.dev> ---
Trying to figure out some other issue with the spec and forgot to mention it.
help2man was suggested to me by code@music, and I'm very pleased with the
result.
Being used in my own spec here:
https://github.com/ppfeister/pkg/blob/master/sherlock/sherlock-project.spec
Note L55-61 in %install:
```
install -d '%{buildroot}%{_mandir}/man1'
PYTHONPATH='%{buildroot}%{python3_sitelib}' help2man \
--no-info \
--version-string='%{version}' \
--name='%{summary}' \
--output='%{buildroot}%{_mandir}/man1/sherlock.1' \
'%{buildroot}%{_bindir}/sherlock'
```
And L72 in %files:
```
%{_mandir}/man1/sherlock.1*
```
Fairly easily adaptable.
For each bin that you want to generate a man page for, swap `sherlock` with the
name of the file.
The only problem was that you've got a bakers dozen different files being
installed that may (or may not) each warrant their own man page -- I'm debating
if there's a more 'friendly' way to address it rather than repeating that
entire chunk 13 times. Possibly expanding a loop, but that's still not the
prettiest.
If looped somehow, the 'sed's can be dropped to just one and included in the
loop as well...... in theory.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2252811
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...