| 1 |
On Tue, 22 Aug 2017 05:16:55 -0400, |
| 2 |
Neil Bothwick wrote: |
| 3 |
> |
| 4 |
> [1 <text/plain; utf-8 (quoted-printable)>] |
| 5 |
> [2 <text/html; utf-8 (quoted-printable)>] |
| 6 |
> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - - newuse @world to apply the change. The depclean should work, |
| 7 |
> Just check for stray ruby settings in /etc/portage. |
| 8 |
> |
| 9 |
> On 22 August 2017 05:21:23 EEST, John Covici <covici@××××××××××.com> wrote: |
| 10 |
> |
| 11 |
> On Mon, 21 Aug 2017 21:20:04 -0400, |
| 12 |
> Alec Ten Harmsel wrote: |
| 13 |
> |
| 14 |
> |
| 15 |
> |
| 16 |
> On 08/21/2017 10:13 AM, allan gottlieb wrote: |
| 17 |
> |
| 18 |
> |
| 19 |
> I issued emerge --pretend --verbose --depclean =ruby-2.1.9 |
| 20 |
> and the response was |
| 21 |
> |
| 22 |
> dev-lang/ruby |
| 23 |
> selected: 2.1.9 |
| 24 |
> protected: none |
| 25 |
> omitted: 2.2.6 |
| 26 |
> |
| 27 |
> Am I correct in believing it is now safe to issue |
| 28 |
> |
| 29 |
> emerge --depclean =ruby-2.1.9 |
| 30 |
> |
| 31 |
> thanks, |
| 32 |
> allan |
| 33 |
> |
| 34 |
> |
| 35 |
> Yes, that should be fine. I rarely look at portage output and |
| 36 |
> just run `emerge -uDN @world' and `emerge --depclean' right after |
| 37 |
> one another, and it always works fine for ruby/python upgrades. |
| 38 |
> |
| 39 |
> The devs have done such a good job in general that I haven't had |
| 40 |
> any problems just running these commands the past couple years. |
| 41 |
> |
| 42 |
> I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the |
| 43 |
> default, but when I ran emerge --depclean I still have packages |
| 44 |
> pulling ruby21 as follows: |
| 45 |
> |
| 46 |
> Calculating dependencies .. ..... done! |
| 47 |
> dev-lang/ruby-2.1.10 pulled in by: |
| 48 |
> dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1 |
| 49 |
> dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1 |
| 50 |
> dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1 |
| 51 |
> dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1 |
| 52 |
> dev-ruby/maruku-0.7.3 requires dev-lang/ruby:2.1 |
| 53 |
> dev-ruby/minitest-5.10.3 requires |
| 54 |
> dev-lang/ruby:2.1 |
| 55 |
> dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1 |
| 56 |
> dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1 |
| 57 |
> dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1 |
| 58 |
> dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1 |
| 59 |
> dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1 |
| 60 |
> dev-ruby/rubygems-2.6.12 requires |
| 61 |
> dev-lang/ruby:2.1 |
| 62 |
> dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1 |
| 63 |
> dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1 |
| 64 |
> virtual/rubygems-13 requires dev-lang/ruby:2.1 |
| 65 |
> virtual/rubygems-7 requires dev-lang/ruby:2.1 |
| 66 |
> |
| 67 |
> I tried a word ld update, but it didn't update any of those packages |
| 68 |
> -- any ideas of how to fix? |
| 69 |
> |
| 70 |
|
| 71 |
I use the following arguments when I run updates: |
| 72 |
--update --deep --with-bdeps=y --changed-use --backtrack=120 |
| 73 |
--keep-going world |
| 74 |
|
| 75 |
Do I need to use new-use instead? |
| 76 |
|
| 77 |
-- |
| 78 |
Your life is like a penny. You're going to lose it. The question is: |
| 79 |
How do |
| 80 |
you spend it? |
| 81 |
|
| 82 |
John Covici |
| 83 |
covici@××××××××××.com |
Archives