@pmatilai commented on this pull request.


> @@ -430,6 +438,10 @@ typedef enum rpmSigTag_e {
     RPMSIGTAG_SHA256   = RPMTAG_SHA256HEADER,
     RPMSIGTAG_FILESIGNATURES           = RPMTAG_SIG_BASE + 18,
     RPMSIGTAG_FILESIGNATURELENGTH      = RPMTAG_SIG_BASE + 19,
+    RPMSIGTAG_VERITYSIGNATURES         = RPMTAG_SIG_BASE + 20,
+    RPMSIGTAG_VERITYSIGNATURELENGTH    = RPMTAG_SIG_BASE + 21,
+    RPMSIGTAG_VERITYSIGNATUREALGO      = RPMTAG_SIG_BASE + 22,
+    RPMSIGTAG_VERITYSIGNATUREBLKSZ     = RPMTAG_SIG_BASE + 23,

Allowing for options (eg at distro level) is not the issue, the real issue is 
that for this to be a generally meaningful feature for rpm at all, these 
signatures need to be architecture and filesystem independent. For rpm it's all 
the same whether the block size is big or small as long as its consistent 
across all architectures, we can't have essentially arch-specific signatures in 
a noarch package. So this seems like quite a deal-breaker to me, unless I'm 
misunderstanding something (which is certainly possible).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1203#discussion_r432288920
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to