LSB RPM format needs to support multiple Provides

[Jeff Johnson]

Created attachment 2331 [details]
results of that egrep

Through historical practice, the LSB RPM format only permits a single Provides

Modern rpmbuild script practice has added SO and arch versioning, and more:

19:38 mwichmann> licquia: I'm getting same error as in the mail about
                  RPMTAG_PROVIDENAME on the libbat I build, which of course
                  contains shared libs
19:38 mwichmann> Simple check here:
19:38 mwichmann> $ rpm -qp --provides lsb-build-libbat*
19:38 mwichmann> lsb-build-libbat-5.0 = 1.1-2.lsb5
19:38 mwichmann> lsb-build-libbat-5.0(x86-64) = 1.1-2.lsb5
19:38 mwichmann> and then pkgchk (called by the libbat verify step) screams

We need to support this in our tools (to create a test case, and to test for
it), and our specification

Question arises if this is a simple re-determination of scope (and so can be
slipstreamed into back revisions with an editorial note, or of we need to track
a: Not-Before: indicator

The attachment seem to enumerate the 'touch points
$ egrep -R RpmTag * > all_RpmTag.txt