Howdy, Can someone point me to any documentation on why ebuilds are being created for ruby gems?
Gem is the a nice, easy to use, standard package manager for ruby. The problem that I see is if you install the same package via both gem and portage all sorts of bad things happen. For the curious, use gem to install rake, then portage to install rake, then try to use rake... Hint, emerge --unmerge is your friend. The real problem is when you now install a package that has ruby dependencies (example kazehakase-0.4.1). Real easy to to have portage trash your previous gem install. Wouldn't make more sense to have the ebuilds front-end gem vs. doing a config & make & make instlal? Then if you had installed via gem, then portage, the gem would just be re-installed, not installed differently. TIA, Roy -- echo "spzxAdjtdp/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge' -- gentoo-dev@gentoo.org mailing list
