Dne 15. 06. 21 v 19:34 Ewoud Kohl van Wijngaarden napsal(a):
On Tue, Jun 15, 2021 at 01:51:12PM +0200, Miro Hrončok wrote:
On 15. 06. 21 13:46, Vitaly Zaitsev via devel wrote:
If that is not possible with reasonable effort,
at least a basic smoke test (such as importing the packaged module)
*MUST* be run in `+%check+`.
A simple scriplet should be introduced I think:
%check
%do_import_test
Already on it:
https://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/99
This may be not be the right place, but in Foreman's Ruby packaging
we've also felt a similar pain. Mostly with C extensions that were
built in the wrong directory. We also added a %check section to do a
basic "import" (require) test.
Is there a similar macro for Ruby smoke testing?
No, there is no similar macro for Ruby. Historically, it was not clear
what should be actually required. With Bundler putting into place more
conventions, the situation is better.
Nevertheless, what is the specific issue you are referring to above?
There are many examples of fixing such issue, e.g.
https://src.fedoraproject.org/rpms/rubygem-bcrypt/blob/rawhide/f/rubygem-bcrypt.spec#_52
And there are probably more complex cases.
And for those of us who also maintain packages for EL7/8, what's the
availability of these macros?
RHEL7 is in Maintenance Support 2 Phase [1], so don't expect too much.
There are better chances to get such macro into RHEL8, but in the
context of Ruby, there are 3 supported versions ATM, therefore it might
get complex.
Anyway, it is good idea to use such macros in the following way:
~~~
%{?import_smoke_test}
~~~
This does the right thing where such macro is supported and is ignored
elsewhere, where such macro is not available.
Vít
[1] https://access.redhat.com/support/policy/updates/errata
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
