1 |
John Covici wrote: |
2 |
> On Tue, 22 Aug 2017 05:16:55 -0400, |
3 |
> Neil Bothwick wrote: |
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 |
> I use the following arguments when I run updates: |
71 |
> --update --deep --with-bdeps=y --changed-use --backtrack=120 |
72 |
> --keep-going world |
73 |
> |
74 |
> Do I need to use new-use instead? |
75 |
> |
76 |
|
77 |
Over the years, I've updated my update process to what causes the least |
78 |
issues, for me at least. This is what I type in: |
79 |
|
80 |
eix-sync && emerge -uaDN world |
81 |
|
82 |
This is the settings I have in make.conf: |
83 |
|
84 |
EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j8 |
85 |
--quiet-build=n -1 --unordered-display" |
86 |
|
87 |
Obviously some may need to be set differently, like the -j8 part, for |
88 |
your system but some of that helps no matter what system you use. The |
89 |
-1 for example keeps the world file clean since you have to put effort |
90 |
into adding something to it. One could add it to the world file |
91 |
directly or use the --select y option. Either way, nothing gets added |
92 |
to the world file because you forgot to use the -1 option. The |
93 |
backtrack, so far 100 has worked. If I start to have issues that a |
94 |
higher number fixes, it will be upped to that number. Over time, some |
95 |
things have been removed since they were no longer needed. |
96 |
|
97 |
Your mileage may vary but could give you a good starting point. Took me |
98 |
years to get to that simple line. ;-) If anyone is interested, I could |
99 |
post some other things from make.conf I've picked up over the years. |
100 |
|
101 |
Hope that helps. |
102 |
|
103 |
Dale |
104 |
|
105 |
:-) :-) |