[Rpm-maint] [rpm-software-management/rpm] Add a man page for RPM dependency generators (PR #3957)

[Panu Matilainen]

@pmatilai commented on this pull request.



> +
+## Tunables
+*%\_\_*_NAME_*\_conflicts_opts* _BODY_++
+*%\_\_*_NAME_*\_enhances_opts* _BODY_++
+*%\_\_*_NAME_*\_obsoletes_opts* _BODY_++
+*%\_\_*_NAME_*\_orderwithrequires_opts* _BODY_++
+*%\_\_*_NAME_*\_provides_opts* _BODY_++
+*%\_\_*_NAME_*\_recommends_opts* _BODY_++
+*%\_\_*_NAME_*\_requires_opts* _BODY_++
+*%\_\_*_NAME_*\_suggests_opts* _BODY_++
+*%\_\_*_NAME_*\_supplements_opts* _BODY_
+
+*%\_\_requires_exclude* _REGEX_++
+*%\_\_requires_exclude_from* _REGEX_++
+*%\_\_provides_exclude* _REGEX_++
+*%\_\_provides_exclude_from* _REGEX_

Hmm. This kinda circles back to the man fileattr vs depgen man page split we've been talking about elsewhere, but:

I think it'd be useful to separate file attributes and generators in the synopsis. The former are attribute global (matching rules, flags, protocol) whereas the latter are per dependency type. So something like

File attributes:
- NAME_path
- ...

Generators
- NAME_conflicts...
- ...

Generator tunables
- NAME_conflicts_opts
- NAME_conflicts_exclude
- ...

One possible way to deal with the explosion of items due to the per-dep things is introduce them as __NAME_DEPTYPE_foo and then have an Example section in the SYNOPSIS that demonstrates it for eg the requires type.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3957#discussion_r2367129648
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/3957/review/3251182900 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20250922/a3bc5df1/attachment.htm>