John Covici wrote: > On Tue, 22 Aug 2017 05:16:55 -0400, > Neil Bothwick wrote: >> [1 <text/plain; utf-8 (quoted-printable)>] >> [2 <text/html; utf-8 (quoted-printable)>] >> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - - >> newuse @world to apply the change. The depclean should work, >> Just check for stray ruby settings in /etc/portage. >> >> On 22 August 2017 05:21:23 EEST, John Covici <cov...@ccs.covici.com> wrote: >> >> 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? >> > I use the following arguments when I run updates: > --update --deep --with-bdeps=y --changed-use --backtrack=120 > --keep-going world > > Do I need to use new-use instead? >
Over the years, I've updated my update process to what causes the least issues, for me at least. This is what I type in: eix-sync && emerge -uaDN world This is the settings I have in make.conf: EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j8 --quiet-build=n -1 --unordered-display" Obviously some may need to be set differently, like the -j8 part, for your system but some of that helps no matter what system you use. The -1 for example keeps the world file clean since you have to put effort into adding something to it. One could add it to the world file directly or use the --select y option. Either way, nothing gets added to the world file because you forgot to use the -1 option. The backtrack, so far 100 has worked. If I start to have issues that a higher number fixes, it will be upped to that number. Over time, some things have been removed since they were no longer needed. Your mileage may vary but could give you a good starting point. Took me years to get to that simple line. ;-) If anyone is interested, I could post some other things from make.conf I've picked up over the years. Hope that helps. Dale :-) :-)
