Hello,
right now, spec files do not have any 'type' identifier, which means, they all
need to be treated the same way in a distribution. If they contained a class
specifier, there could be two (or more) types of packages, each with a
different set of requirements given to them by a distribution standard (e.g.
Fedora Packaging Guidelines for Fedora distribution). This might be very useful
because with containers, the rpm packages can be constrained less heavily in
what they can do in the system. At the same time, it will be useful to mark
those packages as having those extended capabilities so that user (and tooling
like a package manager) knows what to expect from them. That's why this
information should be ideally stored in rpm header to be easily accessible to
everyone.
--
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/issues/236
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
