How do you know if the package was built with an older rpm vs. the new rpm? If
you can ascertain that, then you can surely have the latest rpm complain/warn
if it finds an rpm built with the latest rpm that doesn't have the tags, while
older rpm would be blissfully unaware, happy, and able to use an rpm generated
by the latest rpm.
It just feels like straight-forward backwards compatibility support (which
would be opt-in, and could emit a warning when you try to do it) would not be
that difficult to maintain here, and would make a number of users lives much
easier. Most people would never even know they could do this, because they only
use rpm via dnf or rpmbuild scripts, which would NOT be setting this optional
flag. Admittedly, the number of people who would need/want this feature would
be minimal, but I'm still not seeing why it would be so terrible to carry a few
extra lines of code here.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2727#issuecomment-1980970565
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2727/1980970...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
