Vít Ondruch píše v St 22. 02. 2017 v 10:01 +0100:
No I feel ashamed that although I was lobbying for gcc BR, I never
used it in my packages. So thank you František for doing so (I assume
that you were forced to do so due to gcc missing in buildroot,
Actually it was just to fulfill guidelines (I learned from Mamoru
during doing review, that there is C/C++ specific guidelines, which
I've missed :-)).
So it is not needed right now in existing packages.
Now I just wonder, wouldn't it be better to add these requires
ruby-devel? Although one can BR: ruby-devel just because of the
macros, so this would be unnecessary.
So my other idea is to modify gem2rpm to add the requires whenever
the gem has binary extension. There might be false positives as well,
but one should review the otput of gem2rpm, so it is possible to
remove the BR in case it is not required.
It looks like both ways are sane and have no big disadvantages? ruby-
devel would simplify things. On other hand dependency from gem2rpm will
put gcc in the place, where is known it is needed.