As I posted on the mailing list, this is something that I do every now and then to help new packages that may not be aware of these guidelines. E.g., I recently detected that opentoonz wasn't compliant, so I helped the maintainer do the porting. I also found a couple of older packages silently opting out without any notice or explanation, so I opened BZ reports and I'm trying to help them solve the possible issues they may have.
I made a small script (published here) that performs these checks, and reports packages that violate the guidelines as well as the libraries they link to. E.g., we have now:
$ ./check_blaslapack.py freefem++ : libcblas.so.3()(64bit), liblapack.so.3()(64bit), libopenblas.so.0()(64bit) openmeeg : libopenblas.so.0, libopenblas.so.0()(64bit) opentoonz : libcblas.so.3()(64bit)
It would be nice to automatically run this once some time before each release (with enough time to react), and open BZ issues for the reported packages. I'd be happy to contribute this script to releng and to be in CC of such BZs to help with the porting. I'm not sure though whether it should exist some specific FESCo policy about it before.
Metadata Update from @mhayden: - Issue tagged with: meeting
@iucar We talked about this in today's FESCo Meeting and we agreed that anyone who is a contributor or is interested in checking these should run the script and submit bugs when needed. No special privileges are required to do that.
However, there's not much interest in running this in releng. We did talk a bit about enabling these checks in rpmlint and/or fedora-review to catch the issue during the review process. @music also mentioned he'd use in his package gating but that's too much for him to maintain on his own.
Metadata Update from @mhayden: - Issue untagged with: meeting
Thanks.
Closing as invalid, meaning nothing to do for fesco.
Metadata Update from @churchyard: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.