Comment # 9 on bug 1207307 from Robert Frohl

(In reply to Marcus R���ckert from comment #8)
> this brings me to the question: what are you trying to do with mkmf?

abusing one of the helper functions ;), i.e. find_executable(). I did not want
to iterate over everything in PATH manually and aiming for something that is
not linux specific.

(In reply to Marcus R���ckert from comment #7)
> mkmf == make makefile. yes mkmf has some nice helper functions which might
> be useful outside of the scope of creating makefiles for ruby extensions,
> but in general you can consider those provide to the library. given the
> scope of mkmf, expecting it only to work when the devel files are around a
> given. that's why I say if we change anything, then we move the that library
> to the devel package.

I would agree that my use case is kinda on the fringe side. Thought I wanted to
try a bit more to convince you. I am okay close, if that did not work out ;)