On 11/12/2013 00:11, Norman Invasion wrote: > On 10 December 2013 15:33, Alan McKinnon <[email protected]> wrote: >> >> On 10/12/2013 20:28, Bruce Hill wrote: >>> On Tue, Dec 10, 2013 at 05:52:36PM +0200, Alan McKinnon wrote: >>>> >>>> The only thing portage can do is assume you want everything to work >>>> under all installed interpreters. If you want to restrict the list of >>>> installed interpreters, use the relevant settings in make.conf. Python >>>> has PYTHON_TARGETS and SINGLE_PYTHON_TARGET for this, I don't know what >>>> the ruby equivalent is. >>>> -- >>>> Alan McKinnon >>>> [email protected] >>> >>> mingdao@workstation ~ $ grep ruby /etc/portage/make.conf >>> RUBY_TARGETS="ruby20" >>> >>> Can't imagine you didn't know that. Ruby hater? :D >>> >> >> >> You could say that: >> >> $ grep -ir -C1 ruby /etc/portage >> /etc/portage/package.use/package.use- # I see no need for lvm thin >> volumes. And it needs thin-provisioning-tools >> /etc/portage/package.use/package.use: # which needs ruby. I do not want >> ruby. >> /etc/portage/package.use/package.use- sys-fs/lvm2 -thin >> >> >> >> But the real reason I don't have ruby is I don't have a use for it >> > > $ cat /etc/portage/package.mask > dev-lang/ruby* > dev-ruby/* > > Because sh, bash, awk, make, scons, cmake, perl, > & two different version of python certainly aren't enough.
You left out sed :-) -- Alan McKinnon [email protected]
