From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE ruby_targets_ruby20
Date: Fri, 15 Nov 2013 14:10:17 -0500 [thread overview]
Message-ID: <52867199.7060801@libertytrek.org> (raw)
In-Reply-To: <CAJnEOsj_M-3yF-gNokTc2vdC8T3eedmpHO4xVWdZ2fVPvyHV0g@mail.gmail.com>
On 2013-11-15 5:56 AM, Daniel Pielmeier <billie@gentoo.org> wrote:
> 2013/11/15 Adam Carter <adamcarter3@gmail.com
> <mailto:adamcarter3@gmail.com>>
> >
> > Not an answer to your question, but yesterday ruby got pulled in by
> an update to thin-provisioning-tools, which was required by lvm2.
> >
>
> It looks like ruby is only required for the tests of
> sys-block/thin-provisioning-tools [1].
>
> The new ebuild thin-provisioning-tools-0.2.8-r1 reflects this. So if you
> update to this version and don't use FEATURES="test" it should not pull
> in ruby anymore.
>
> [1]
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-block/thin-provisioning-tools/ChangeLog?r1=1.26&r2=1.27
Ok, so... is there or is there not a way to prevent ruby from being
installed?
I've tried adding -ruby and -test to package.mask for
thin-provisioning-tools, and even tried adding them to USE= in
make.conf, to no avail...
next prev parent reply other threads:[~2013-11-15 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 23:57 [gentoo-user] USE ruby_targets_ruby20 Chris Stankevitz
2013-11-15 1:24 ` Adam Carter
2013-11-15 10:56 ` Daniel Pielmeier
2013-11-15 13:33 ` Tanstaafl
2013-11-15 13:43 ` Daniel Pielmeier
2013-11-15 15:29 ` Chris Stankevitz
2013-11-15 15:34 ` Daniel Pielmeier
2013-11-15 19:10 ` Tanstaafl [this message]
2013-11-15 20:01 ` Chris Stankevitz
2013-11-15 21:58 ` Tanstaafl
2013-11-15 22:18 ` Alan McKinnon
2013-11-16 13:10 ` Tanstaafl
2013-12-16 11:50 ` LVM - is thin provisioning used? - WAS " Tanstaafl
2013-11-15 5:28 ` Mark David Dumlao
2013-11-15 7:15 ` [gentoo-user] " Hans de Graaff
2013-11-15 15:45 ` 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=52867199.7060801@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--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