public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boris Fersing" <kernelsensei@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ruby gems vs. ebuilds
Date: Thu, 5 Oct 2006 22:16:06 +0200	[thread overview]
Message-ID: <97c95c3d0610051316y4577bf75tb14ddd70799b4824@mail.gmail.com> (raw)
In-Reply-To: <4525650C.3060805@cisco.com>

2006/10/5, Roy Wright <royw@cisco.com>:
> 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



  reply	other threads:[~2006-10-05 20:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 20:03 [gentoo-dev] ruby gems vs. ebuilds Roy Wright
2006-10-05 20:16 ` Boris Fersing [this message]
2006-10-05 21:03   ` Roy Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=97c95c3d0610051316y4577bf75tb14ddd70799b4824@mail.gmail.com \
    --to=kernelsensei@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox