All of the I18N string tags (SUMMARY/DESCRIPTION/CHANGELOG*) should not be
included in IDENTITY because the value returned can depend on an envvar, and/or
external files, and/or macros embedded in text.
Then there are issues with the stat(2) links, where st_mtime/st_rdev/st_inode
tags should
There are two meanings for "used": instantiated in the header and summed
within IDENTITY.
Newly defined/added tags will not be part of IDENTITY if positive/inclusive
logic is used (as said repeatedly).
Tags that were previously present in header/IDENTITY and were dropped will be a
change of
One of main task to solve: what we should do with tags that were used
previously and do not used now, and tags that can be added in the future, but
are not present in rpm now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Panu pointed out that using the immutable region header instead of the rpmdb
header gets rid of all the remapped signature tags and appended tags, thereby
shortening the list above considerably.
The logic still needs to become positive/inclusive to ensure the IDENTITY tag
set is both well
The previous discussion was
[here](http://lists.rpm.org/pipermail/rpm-maint/2018-April/007718.html).
Main thought:
- compute identity as a digest of filtered iterated pair of tags and its values
of immutable header region;
- change the awk script that generates the tag table to add a marker
There was a suggestion to [calculate RPMTAG_IDENTITY as tag
extension](http://lists.rpm.org/pipermail/rpm-maint/2018-March/007688.html) and
do not the tag to actual rpm package during build time.
The main idea is to take message digest from package header tags filtered by
the blacklist
