On Mon, 21 Aug 2017 21:20:04 -0400, Alec Ten Harmsel wrote: > > > On 08/21/2017 10:13 AM, allan gottlieb wrote: > > > > I issued emerge --pretend --verbose --depclean =ruby-2.1.9 > > and the response was > > > > dev-lang/ruby > > selected: 2.1.9 > > protected: none > > omitted: 2.2.6 > > > > Am I correct in believing it is now safe to issue > > > > emerge --depclean =ruby-2.1.9 > > > > thanks, > > allan > > > > Yes, that should be fine. I rarely look at portage output and > just run `emerge -uDN @world' and `emerge --depclean' right after > one another, and it always works fine for ruby/python upgrades. > > The devs have done such a good job in general that I haven't had > any problems just running these commands the past couple years.
I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the default, but when I ran emerge --depclean I still have packages pulling ruby21 as follows: Calculating dependencies .. ..... done! dev-lang/ruby-2.1.10 pulled in by: dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1 dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1 dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1 dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1 dev-ruby/maruku-0.7.3 requires dev-lang/ruby:2.1 dev-ruby/minitest-5.10.3 requires dev-lang/ruby:2.1 dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1 dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1 dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1 dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1 dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1 dev-ruby/rubygems-2.6.12 requires dev-lang/ruby:2.1 dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1 dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1 virtual/rubygems-13 requires dev-lang/ruby:2.1 virtual/rubygems-7 requires dev-lang/ruby:2.1 I tried a word ld update, but it didn't update any of those packages -- any ideas of how to fix? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com