2006/10/5, Roy Wright <[EMAIL PROTECTED]>:
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.
Hi,
AFAIK, the ruby related ebuilds use gem. For example rails has in his ebuild :
"inherit ruby gems"
and if you look in the gems eclass :
<code>
gems_src_install() {
gems_location
if [ -z "${MY_P}" ]; then
GEM_SRC=${DISTDIR}/${P}
else
GEM_SRC=${DISTDIR}/${MY_P}
fi
if use doc; then
myconf="--rdoc"
else
myconf="--no-rdoc"
fi
dodir ${GEMSDIR}
gem install ${GEM_SRC} -v ${PV} ${myconf} -l -i ${D}/${GEMSDIR} ||
die "gem install failed"
if [ -d ${D}/${GEMSDIR}/bin ] ; then
exeinto /usr/bin
for exe in ${D}/${GEMSDIR}/bin/* ; do
doexe ${exe}
done
fi
}
</code>
And it's the same for rake !
The problem might be (that's a supposition only) that gem installs the
files in the image which will be merged to the system by portage and
doesn't install the files directly in the "real" system.
or maybe did I miss something ?
Regards,
Boris.
TIA,
Roy
--
echo "spzxAdjtdp/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
--
gentoo-dev@gentoo.org mailing list
--
Quiconque me parle de Dieu en veut à ma bourse ou à ma liberté.
--
gentoo-dev@gentoo.org mailing list
