Dne 25.1.2016 v 18:58 Mattias Ellert napsal(a):
mån 2016-01-25 klockan 18:09 +0100 skrev Marcin Juszkiewicz:
> W dniu 25.01.2016 o 17:03, Vít Ondruch pisze:
>> So it appears this thread was probably not enough. Which keeps us with
>> interesting state where mock by default does not install weak
>> dependencies where Koji installs them. It causes interesting issues already.
> mock/koji not installing weak dependencies == anything wanting ruby
> being broken.
Yep, I know. Believe or not, this is precisely how I found out that Koji
installs the weak dependencies while mock does not.
> Reason: "ruby" suggests "rubypick" which suggests
> Packages buildrequire "ruby" but do not get "rubypick" installed
> they are lucky they get) so are unable to find Ruby because there is no
> "/bin/ruby" executable.
If ruby needs ruby-pick to work, then ruby-pick must not be a weak
dependency of ruby, but a hard one.
The thing is that ruby does not need rubypick to work, but you have to
call ruby-mri instead of ruby in this case. This of course allows you to
avoid rubypick on your system in case you really know what you are doing.
For some moment, I was thinking to add rubypick as dependency of
ruby-devel, but decided against it (at least for the time being), since
there are several reasons for the situation and multiple ways how to fix
it. Just several examples which comes to my mind:
1) There are chances that the build does not need the ruby executable at
all, since it just want to have headers for build.
2) The configure script can be configured what Ruby executable should be
3) There can be explicit BR: /usr/bin/ruby
I'd love to take this opportunity to gain knowledge how all these
projects are actually using Ruby.