> What if we shipped in rubygems-devel some
fake libraries, which would try to load the original library, but
silently provided the miminum mock to make the test suite pass without
the library?
You mentioned about including the logic in "rubygems-devel" RPM.
I misunderstood you mentioned about "ruby-devel".
rubygems-devel package includes below files, that have macros for
rubygems RPM packaging.
When a user install current rubygems-devel, that is not still harmful,
that's not confusing a user.
But after including the fake libraries in it, if user install the
rubygems-devel by mistake, it is harmful.
ruby.spec
```
%files -n rubygems-devel
%{_rpmconfigdir}/macros.d/macros.rubygems
%{_rpmconfigdir}/fileattrs/rubygems.attr
%{_rpmconfigdir}/rubygems.req
%{_rpmconfigdir}/rubygems.prov
%{_rpmconfigdir}/rubygems.con
```
--
Jun Aruga / He - His - Him
_______________________________________________
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org
To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.org
