pmatilai created an issue (rpm-software-management/rpm#4003)
Rpm tag info is scattered around in rather hackish way - the name-value is an
actual enum, but then a bunch of information is encoded inside a comment from
which it gets awk'ed into a struct that librpm actually uses. And then we have
tags.md describing these things, duplicating name/value/type just to include
description. We completely lack the information about tag relations outside
program code logic.
We should move this all to a single file (something like a json file) that acts
as a canonical source of truth for all tag info, from which we can generate
rpmtag.h, the tags man page, package verification etc.
The tag info file should contain at least the existing info:
- name
- value
- type
- concrete/extension/obsolete/deprecated/internal flag(s)
- description
...but should also carry information about package relations
- A indexes B
- if any tag from set A, B, C... is present, the entire set of tags must be
present
- optionality of a tag (required, optional, conditional - see above)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/4003
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
