Hello Michael. Long time no read. ;-)
> I think the best way to support that in a package is to declare which
> ruby versions are supported with USE_RUBY and ruby-ng.eclass.
I tried what you suggested. However, inheriting from ruby-ng.eclass
introduces an odd problem: For some reason unknown to me, "${S}" no
longer matches the default value of "${WORKDIR}/${P}", but only what I'd
expect in "${WORKDIR}". That means the base directory for src_compile
and src_install is not correct, causing the build to fail. It might be a
bug in ruby-ng, or a side effect of inheriting from ruby-ng on top of
the other eclasses already needed/used by the ebuild. I don't feel
comfortable with opening this particular can of worms when only a single
library something.so needs to be installed. Right now, I changed to
this:
local p=$(ruby -e 'puts $LOAD_PATH' | grep 'vendor.\+linux')
[[ -d "${p}" ]] || die "'${p}' is not a directory"
exeinto "${p}"
Not very pretty either, but at least this avoids any hardcoded
directories.
-Ralph
