xmminintrin.h packaging in a gcc (and arch) specific sub directory is hardly a
compelling usage case for addition of %optional to rpm: gcc is hard packaging
no matter what, and adding a generally available %optional everywhere in rpm is
an invitation for abuse, if the only justification is a couple of lines less
typing in a couple of spec files.
It's not overly hard to generate a dynamic file list using find, and then
filter out the specific language files in per-language file manifests. Explicit
manifests through scripting is arguably easier to maintain/debug than
attempting explicit %optional markers on the union of all possible per-language
manifests (which surely breaks on any significant file additions) so that a
single static manifest can be used for all per-language subpackages,
Meanwhile, it's hardly worth arguing the points either then or now.
Particularly when %optional is entirely undocumented: there's a huge ripple
effect of a spec file syntax change adoption through multiple distro's and
packaging committees and packagers. It's hardly worth the several years of
churn that will precede adoption (and the ensuing legacy incompatibilities).
At a minimum, documentation needs to be attempted, and perhaps opinions from
the 1-2 packagers who might find your usage cases compelling.
--
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/417#issuecomment-373246834
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
