The ruby.eclass file assumes that it has a GNU version of the cp command. Therefore, trying to install a ruby package that contains examples documentation will fail when ebuild tries to execute "cp -a". (Rubygems is an example of such a package.) Reproducible: Always Steps to Reproduce: 1. emerge rubygems Actual Results: Failure during the install phase of the ebuild: * running dodoc for ruby ;) cp: illegal option -- a usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src1 ... srcN directory Expected Results: Correctly installed and merged the package.
Created attachment 61783 [details, diff] Proposed fix This modification to ruby.eclass is more portable. It's not techinically equivalent, but I doubt that any ruby documentation will contain hard links. ;)
Ruby herd: What do you think?
Is this not a problem in a whole bunch of ebuilds, moreso than just ruby? I would think a more global approach might be a slightly better way to tackle it, but from a purely local point I think it's fine.
(In reply to comment #3) > Is this not a problem in a whole bunch of ebuilds, moreso than just ruby? I > would think a more global approach might be a slightly better way to tackle it, Currently, the official stance is to correct any instances of this problem using the proposed fix (see patch). > but from a purely local point I think it's fine. Fixed in CVS. Thanks. :)
