From: kwkhui@hkbn.net
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Understanding new ruby dependencies
Date: Wed, 23 May 2012 02:32:52 +0800 [thread overview]
Message-ID: <20120523023252.57927f37@gentoo-main.kwkh-home> (raw)
In-Reply-To: <CAPi0pstbOb=hStepXE3kp-9cFrWpvc4TwZCeo5R81syOKoheXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
On Tue, 22 May 2012 11:01:45 -0700
Chris Stankevitz <chrisstankevitz@gmail.com> wrote:
> Apparently I have to add some ruby_targets_ruby19 USE flags to my
> system.
No! Don't do that! Instead, you should add a line
RUBY_TARGETS=ruby19
in your make.conf (or RUBY_TARGETS="ruby18 ruby19") and let portage do
the USE_EXPAND to ruby_targets_ruby19 (respectively,
ruby_targets_ruby18 ruby_targets_ruby19) itself for the relevant
packages. See ${PORTDIR}/profiles/desc/ruby_targets.desc for
description. It is much easier and more intuitive this way, since you
are not doing weird things like building package A for ruby18 but not
package B.
> Question 2: Does it seem weird that portage wants me to add USE flags
> to enable some feature in a package I never heard of and have no
> interest in and to top it off has a very weird name
> (ruby_targets_ruby19)?
The "weird" name is a result of USE_EXPANDing RUBY_TARGETS, just like
LINGUAS and SANE_BACKENDS, for example.
Kerwin.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-22 18:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 3:52 [gentoo-user] Understanding new ruby dependencies Chris Stankevitz
2012-05-22 6:07 ` [gentoo-user] " Hans de Graaff
2012-05-22 18:01 ` Chris Stankevitz
2012-05-22 18:32 ` kwkhui [this message]
2012-05-23 1:10 ` Chris Stankevitz
2012-05-23 3:16 ` Michael Orlitzky
2012-05-23 5:13 ` kwkhui
2012-05-23 6:35 ` Chris Stankevitz
2012-05-23 6:37 ` Chris Stankevitz
2012-05-23 7:58 ` kwkhui
2012-05-23 18:15 ` Hans de Graaff
2012-05-23 6:35 ` Hans de Graaff
2012-05-23 15:27 ` Chris Stankevitz
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=20120523023252.57927f37@gentoo-main.kwkh-home \
--to=kwkhui@hkbn.net \
--cc=gentoo-user@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