[gentoo-user] USE ruby_targets_ruby20

[gentoo-user] USE ruby_targets_ruby20

[Chris Stankevitz]

Hello,

If possible please phrase your response in a way that will make sense
to someone who was no idea what is ruby, has no desire to learn what
is ruby, and who doesn't [directly] even want ruby on his system.

True or false: The correct way to appease portage's error message
below is to add a bunch of ruby_targets_ruby20 use flags in
/etc/portage/package.use

Thank you,

Chris

===

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by dev-lang/ruby-2.0.0_p247-r1[rdoc]
# required by dev-ruby/racc-1.4.9[ruby_targets_ruby20]
>=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby20
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19]
# required by virtual/rubygems-4
# required by dev-ruby/rake-0.9.6[-test,ruby_targets_ruby19]
# required by dev-ruby/json-1.8.0[-test,-doc,ruby_targets_ruby18]
# required by dev-lang/ruby-2.0.0_p247-r1
# required by sys-block/thin-provisioning-tools-0.2.8
# required by sys-fs/lvm2-2.02.103[thin]
# required by sys-fs/udisks-1.0.4-r5
# required by x11-libs/libfm-0.1.17-r1[udev]
# required by x11-misc/pcmanfm-0.9.10
# required by @selected
# required by @world (argument)
=dev-ruby/racc-1.4.9 ruby_targets_ruby20
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/racc-1.4.9[ruby_targets_ruby19]
=dev-ruby/json-1.8.0 ruby_targets_ruby20
# required by dev-lang/ruby-2.0.0_p247-r1
# required by dev-ruby/racc-1.4.9[ruby_targets_ruby20]
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby18]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19]
# required by virtual/rubygems-4
# required by dev-ruby/json-1.8.0[-test,ruby_targets_ruby19]
>=dev-ruby/rake-0.9.6 ruby_targets_ruby20
# required by dev-lang/ruby-2.0.0_p247-r1
# required by dev-ruby/racc-1.4.9[ruby_targets_ruby20]
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby18]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/json-1.8.0[ruby_targets_ruby19]
=dev-ruby/rubygems-2.0.3 ruby_targets_ruby20

Re: [gentoo-user] USE ruby_targets_ruby20

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

On Fri, Nov 15, 2013 at 10:57 AM, Chris Stankevitz <
chrisstankevitz@gmail.com> wrote:

> Hello,
>
> If possible please phrase your response in a way that will make sense
> to someone who was no idea what is ruby, has no desire to learn what
> is ruby, and who doesn't [directly] even want ruby on his system.
>
> True or false: The correct way to appease portage's error message
> below is to add a bunch of ruby_targets_ruby20 use flags in
> /etc/portage/package.use
>

Not an answer to your question, but yesterday ruby got pulled in by an
update to thin-provisioning-tools, which was required by lvm2.

To minimise the amount of ruby installed, i added RUBY_TARGETS="ruby20" to
make.conf, so the lower version targets weren't installed. If RUBY_TARGETS
is not set, it installs them all.

[-- Attachment #2: Type: text/html, Size: 1223 bytes --]

Re: [gentoo-user] USE ruby_targets_ruby20

[Daniel Pielmeier]

[-- Attachment #1: Type: text/plain, Size: 593 bytes --]

2013/11/15 Adam Carter <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

--
Regards
Daniel Pielmeier

[-- Attachment #2: Type: text/html, Size: 905 bytes --]

Re: [gentoo-user] USE ruby_targets_ruby20

[Tanstaafl]

On 2013-11-15 5:56 AM, Daniel Pielmeier <billie@gentoo.org> wrote:
> 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.

I don't have FEATURES="test" and it still wants to pull all the ruby 
crap in...

I too would appreciate a resolution to this too... unless, of course, 
there is a very good reason to have ruby installed for ongoing maintenance.

Re: [gentoo-user] USE ruby_targets_ruby20

[Daniel Pielmeier]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

2013/11/15 Tanstaafl <tanstaafl@libertytrek.org>

> On 2013-11-15 5:56 AM, Daniel Pielmeier <billie@gentoo.org> wrote:
>
>> 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.
>>
>
> I don't have FEATURES="test" and it still wants to pull all the ruby crap
> in...
>
> I too would appreciate a resolution to this too... unless, of course,
> there is a very good reason to have ruby installed for ongoing maintenance.
>
>

Well the ebuild I did mention above only requires ruby if the test use flag
is enabled. Maybe anything else is pulling it in.

-- 
Regards
Daniel Pielmeier

[-- Attachment #2: Type: text/html, Size: 1412 bytes --]

Re: [gentoo-user] USE ruby_targets_ruby20

[Chris Stankevitz]

On Fri, Nov 15, 2013 at 5:33 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
>> 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.
>
> I don't have FEATURES="test" and it still wants to pull all the ruby crap
> in...

Me too.  I do not specify FEATURES="test" and
thin-provisioning-tools-0.2.8 still wants dev-lang/ruby-2.0.0_p247-r1:

FEATURES="assume-digests binpkg-logs config-protect-if-modified
distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch
preserve-libs protect-owned sandbox sfperms splitdebug strict
unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv
usersandbox usersync"

>=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby20
# required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
# required by dev-lang/ruby-1.9.3_p448[rdoc]
# required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19]
# required by virtual/rubygems-4
# required by dev-ruby/rake-0.9.6[-test,ruby_targets_ruby19]
# required by dev-ruby/json-1.8.0[-test,-doc,ruby_targets_ruby18]
# required by dev-lang/ruby-2.0.0_p247-r1
# required by sys-block/thin-provisioning-tools-0.2.8

Chris

Re: [gentoo-user] USE ruby_targets_ruby20

[Daniel Pielmeier]

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

Chris Stankevitz schrieb am 15.11.2013 16:29:
> On Fri, Nov 15, 2013 at 5:33 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
>>> 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.
>>
>> I don't have FEATURES="test" and it still wants to pull all the ruby crap
>> in...
> 
> Me too.  I do not specify FEATURES="test" and
> thin-provisioning-tools-0.2.8 still wants dev-lang/ruby-2.0.0_p247-r1:

Guys, please read what I have written!

_thin-provisioning-tools-0.2.8-r1_

-- 
-- 
Daniel Pielmeier


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: [gentoo-user] USE ruby_targets_ruby20

[Tanstaafl]

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...

Re: [gentoo-user] USE ruby_targets_ruby20

[Chris Stankevitz]

On Fri, Nov 15, 2013 at 11:10 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> Ok, so... is there or is there not a way to prevent ruby from being
> installed?

Yes

> 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...

Follow these steps:

0. undo whatever you did

1. emerge --sync

2. echo =sys-block/thin-provisioning-tools-0.2.8-r1 ~amd64 >>
/etc/portage/package.keywords

3. update your system

Chris

Re: [gentoo-user] USE ruby_targets_ruby20

[Tanstaafl]

On 2013-11-15 3:01 PM, Chris Stankevitz <chrisstankevitz@gmail.com> wrote:
> Follow these steps:
>
> 0. undo whatever you did

Already did...

> 1. emerge --sync
>
> 2. echo =sys-block/thin-provisioning-tools-0.2.8-r1 ~amd64 >>
> /etc/portage/package.keywords
>
> 3. update your system

Or, I could just echo sys-fs/lvm2 -thin /etc/portage/package.use

Now, the question is, what the heck is thin-provisioning in lvm2, am I 
using it, and if not, do I need it?

I'm pretty sure I'm not using it, but how to be sure?

Re: [gentoo-user] USE ruby_targets_ruby20

[Alan McKinnon]

On 15/11/2013 23:58, Tanstaafl wrote:
> On 2013-11-15 3:01 PM, Chris Stankevitz <chrisstankevitz@gmail.com> wrote:
>> Follow these steps:
>>
>> 0. undo whatever you did
> 
> Already did...
> 
>> 1. emerge --sync
>>
>> 2. echo =sys-block/thin-provisioning-tools-0.2.8-r1 ~amd64 >>
>> /etc/portage/package.keywords
>>
>> 3. update your system
> 
> Or, I could just echo sys-fs/lvm2 -thin /etc/portage/package.use
> 
> Now, the question is, what the heck is thin-provisioning in lvm2, am I
> using it, and if not, do I need it?
> 
> I'm pretty sure I'm not using it, but how to be sure?
> 


Google for "thin-provisioning+in+lvm2", first three hits.

In a nutshell, you can define an LV without actually allocating the
storage yet that you are not using, it gets allocated "on demand" if you
will.

It's similar in concept to the general idea behind sparse files, lazy
initialization, fixed size vs dynamically allocated disks for VMs and do
on: allocate a resource only when you need it.

This lets you over-commit storage space as much of it is not being used
in practice.

If you use thin provisioning, you already know it. There are steps you
must take to put it to use.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] USE ruby_targets_ruby20

[Tanstaafl]

On 2013-11-15 5:18 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 15/11/2013 23:58, Tanstaafl wrote:
>> Now, the question is, what the heck is thin-provisioning in lvm2, am I
>> using it, and if not, do I need it?
>>
>> I'm pretty sure I'm not using it, but how to be sure?

> Google for "thin-provisioning+in+lvm2", first three hits.
>
> In a nutshell, you can define an LV without actually allocating the
> storage yet that you are not using, it gets allocated "on demand" if you
> will.
>
> It's similar in concept to the general idea behind sparse files, lazy
> initialization, fixed size vs dynamically allocated disks for VMs and do
> on: allocate a resource only when you need it.
>
> This lets you over-commit storage space as much of it is not being used
> in practice.
>
> If you use thin provisioning, you already know it. There are steps you
> must take to put it to use.

Thanks Alan...

But fyi, my last questions were more just me talking to myself... of 
course my google-fu is fairly strong, and like you I found all of my 
answers this morning when I searched...

I chose not to use thin provisioning in vmWare because I just don't like 
the idea... maybe irrational, because I do see the advantages.

I'd be curious to learn if anyone here uses it with lvm, and what their 
experience has been - especially, are there any gotcha's to watch out for?

But for now, to rebuild my kernels without lvm thin provisioning (it is 
enabled) and emerge -C thin-provisioning-tools...

LVM - is thin provisioning used? - WAS Re: [gentoo-user] USE ruby_targets_ruby20

[Tanstaafl]

On 2013-11-15 5:18 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 15/11/2013 23:58, Tanstaafl wrote:
>> Now, the question is, what the heck is thin-provisioning in lvm2, am I
>> using it, and if not, do I need it?
>>
>> I'm pretty sure I'm not using it, but how to be sure?

> If you use thin provisioning, you already know it. There are steps you
> must take to put it to use.

Ok, just to complete this thread (I didn't like this answer when it was 
presented - what if I inherited this system? Or, in this case, I 
installed it 8+ years ago, and don't remember for certain *what* I did, 
since it was my first time with any linux distro, much less gentoo?)...

So, a simple question on the lvm list reveals:

lvs -o segtype

will return 'thin' or 'thin-pool' for thin provisioned, or 'linear' (as 
mine did) for thick...

Re: [gentoo-user] USE ruby_targets_ruby20

[Mark David Dumlao]

On Fri, Nov 15, 2013 at 7:57 AM, Chris Stankevitz
<chrisstankevitz@gmail.com> wrote:
> Hello,
>
> If possible please phrase your response in a way that will make sense
> to someone who was no idea what is ruby, has no desire to learn what
> is ruby, and who doesn't [directly] even want ruby on his system.

Not knowing what goes in your system or what's blocking it: that's not
how gentoo works, sorry. It never was and it never will be.

ruby is a programming language, like python, perl, or what not.

When several versions of a programming language are available for
installing some package, which version to use is controlled by a
lang_target_version_number USE flag. These are also conveniently
controlled by a LANG_TARGETS variable in make.conf, which specify the
versions to install globally. e.g. PYTHON_TARGETS.

Portage is complaining that you are trying to install some packages
for ruby 1.9, and others for ruby 2.0.

>
> True or false: The correct way to appease portage's error message
> below is to add a bunch of ruby_targets_ruby20 use flags in
> /etc/portage/package.use

The easiest way to get through your use blocks is to force portage to
install ruby 2.0 globally instead.

RUBY_TARGETS="ruby20"

in make.conf.

>
> Thank you,
>
> Chris
>
> ===
>
> The following USE changes are necessary to proceed:
>  (see "package.use" in the portage(5) man page for more details)
> # required by dev-lang/ruby-2.0.0_p247-r1[rdoc]
> # required by dev-ruby/racc-1.4.9[ruby_targets_ruby20]
>>=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby20
> # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
> # required by dev-lang/ruby-1.9.3_p448[rdoc]
> # required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19]
> # required by virtual/rubygems-4
> # required by dev-ruby/rake-0.9.6[-test,ruby_targets_ruby19]
> # required by dev-ruby/json-1.8.0[-test,-doc,ruby_targets_ruby18]
> # required by dev-lang/ruby-2.0.0_p247-r1
> # required by sys-block/thin-provisioning-tools-0.2.8
> # required by sys-fs/lvm2-2.02.103[thin]
> # required by sys-fs/udisks-1.0.4-r5
> # required by x11-libs/libfm-0.1.17-r1[udev]
> # required by x11-misc/pcmanfm-0.9.10
> # required by @selected
> # required by @world (argument)
> =dev-ruby/racc-1.4.9 ruby_targets_ruby20
> # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20]
> # required by dev-lang/ruby-1.9.3_p448[rdoc]
> # required by dev-ruby/racc-1.4.9[ruby_targets_ruby19]
> =dev-ruby/json-1.8.0 ruby_targets_ruby20
> # required by dev-lang/ruby-2.0.0_p247-r1
> # required by dev-ruby/racc-1.4.9[ruby_targets_ruby20]
> # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby18]
> # required by dev-lang/ruby-1.9.3_p448[rdoc]
> # required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19]
> # required by virtual/rubygems-4
> # required by dev-ruby/json-1.8.0[-test,ruby_targets_ruby19]
>>=dev-ruby/rake-0.9.6 ruby_targets_ruby20
> # required by dev-lang/ruby-2.0.0_p247-r1
> # required by dev-ruby/racc-1.4.9[ruby_targets_ruby20]
> # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby18]
> # required by dev-lang/ruby-1.9.3_p448[rdoc]
> # required by dev-ruby/json-1.8.0[ruby_targets_ruby19]
> =dev-ruby/rubygems-2.0.3 ruby_targets_ruby20
>



-- 
This email is:    [ ] actionable   [x] fyi        [ ] social
Response needed:  [ ] yes          [x] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [x] none

[gentoo-user] Re: USE ruby_targets_ruby20

[Hans de Graaff]

On Thu, 14 Nov 2013 15:57:40 -0800, Chris Stankevitz wrote:

> True or false: The correct way to appease portage's error message below
> is to add a bunch of ruby_targets_ruby20 use flags in
> /etc/portage/package.use

False. These packages should already have this use flag set by default in 
a vanilla Gentoo setup. Perhaps you masked something related to ruby 
already?

Hans

Re: [gentoo-user] Re: USE ruby_targets_ruby20

[Chris Stankevitz]

On Thu, Nov 14, 2013 at 11:15 PM, Hans de Graaff <graaff@gentoo.org> wrote:
> False. These packages should already have this use flag set by default in
> a vanilla Gentoo setup. Perhaps you masked something related to ruby
> already?

Hans,

You are correct.

A year ago I added RUBY_TARGETS="ruby18 ruby19" to my make.conf in
order to get my system to build.  Today I removed the entry from
make.conf and my update continues without error.

At the time I believe the problem was: 'the gentoo base system needed
the ruby19 USE_EXPAND but it was still awaiting approval.  Work around
the problem by adding RUBY_TARGETS="ruby18 ruby19" to make.conf'

Thank you,

Chris