1 |
On Sun, 29 May 2016 08:13:03 -0400, Alan Grimes wrote: |
2 |
|
3 |
> You know what? fuck you. That's what. |
4 |
|
5 |
Helpful, really helpful. |
6 |
|
7 |
> Packages are being updated at such a breakneck pace these days that it |
8 |
> simply isn't humanly possible to review these manually, or even do |
9 |
> anything intelligent if I tried. |
10 |
|
11 |
Indeed, looking at the output of emerge -a before hitting enter is sooo |
12 |
demanding. |
13 |
|
14 |
> Then emerge |
15 |
> got ornery and stopped letting the necessary, cathartic, inevitable, |
16 |
> trainwreck take place, which is actually a good thing because the |
17 |
|
18 |
You really think that breaking people's systems is a good thing? |
19 |
|
20 |
> DO YOU SERIOUSLY THINK I'M THAT STUPID??? SERIOUSLY???? |
21 |
|
22 |
I'll let others form their own opinions on this. |
23 |
|
24 |
> > Furthermore, the current portage doesn't require the revdep-rebuild |
25 |
> > step because |
26 |
> > of the @preserved-rebuild set creation. |
27 |
> |
28 |
> That missfeature is incompatible with how I use my system. I have not |
29 |
> reformatted my hard drive in six years. |
30 |
|
31 |
Only six years? I am using installations that are older than that, even |
32 |
if the hard drives aren't. |
33 |
|
34 |
> The principle way I accomplish that is by prohibiting the growth of |
35 |
> cruft in the system. I cannot tolerate the accumulation of back versions |
36 |
> anywhere in the system except where absolutely necessary. So if it is |
37 |
> possible to re-build broken packages against new versions, I demand that |
38 |
> take place |
39 |
> as quickly as possible such that the system is left in the most pristine |
40 |
> and self-consistent state possible. --- secret of immortality, dude. =\ |
41 |
|
42 |
So a clean but broken system is preferable to having a few older |
43 |
versions of libraries hanging around for half and hour, until they can be |
44 |
safely, and automatically, removed? |
45 |
|
46 |
Anyway, it seems you are well out of date in your understanding of how |
47 |
portage works. preserved-rebuild is rarely needed these days, thanks to |
48 |
the mysteries of subslots, which can do the necessary rebuilding at the |
49 |
point of upgrade. |
50 |
|
51 |
> You |
52 |
> dumb. |
53 |
> shit. |
54 |
> |
55 |
> You literally have no fucking clue do you? |
56 |
|
57 |
You seem to be echoing the thoughts of so many others here. |
58 |
|
59 |
> Do you think I enabled that missfeature they introduced a few years ago |
60 |
> that hid all of the build output so all I got to see was |
61 |
> |
62 |
> installing package (1/400) |
63 |
> installing package (2/400) |
64 |
> installing package (3/400) |
65 |
|
66 |
It's an options, use it or don't use it. If you really want your updates |
67 |
to take longer just so you can see all the GCC output, which makes |
68 |
little sense anyway when MAKEOPTS is set to anything but -j1. |
69 |
Personally, I prefer the Unix approach of succeed quietly, fail noisily. |
70 |
If I see compiler output on my monitor, i know something is wrong. |
71 |
|
72 |
> I am typing this on my smaller monitor because I have the full verbose |
73 |
> build process fullscreen on my 24". That's right, for the last 12 years, |
74 |
> I have watched every single build take place in live time because I've |
75 |
> watched it execute every single compiler invocation, I have watched |
76 |
> every error and warning message. |
77 |
|
78 |
What a sad life you must have. Watching compiler output is even more |
79 |
tedious than reading Twitter! |
80 |
|
81 |
> I do not need log files because I watch everything in live time. |
82 |
|
83 |
And you retain everything you see and never need to refer back to what |
84 |
scrolled off the screen ten minutes ago? |
85 |
|
86 |
> By |
87 |
> doing this, I have learned things about my packages that you fucking |
88 |
> dipshits couldn't imagine. Back before when Gentoo jumped the shark |
89 |
> (tried to force everyone onto libav), the system was completely |
90 |
> self-correcting, If the system set was intact, literally every other |
91 |
> problem would self correct. I didn't need to rant on this list because |
92 |
> everything was perfect. |
93 |
|
94 |
> The problem is that the portage people don't understand how the packages |
95 |
> actually work |
96 |
|
97 |
So there's the problem, all the Gentoo devs are dipshits, as well as all |
98 |
of us. No wonder Gentoo is such a pile of steaming shite. I'm completely |
99 |
flabbergasted that you still consider it worth using. |
100 |
|
101 |
> It wouldn't let me do that because it was throwing a conflict message |
102 |
> for libreoffice so I was forced to temporarily uninstall it to clear a |
103 |
> block message, fuck you again portage... |
104 |
|
105 |
Have you read the emerge and portage man pages anytime in the last five |
106 |
years? |
107 |
|
108 |
> IQ is a measure of how stupid you feel. |
109 |
|
110 |
What measures how stupid you act? |
111 |
|
112 |
|
113 |
-- |
114 |
Neil Bothwick |
115 |
|
116 |
What do you have when you have six lawyers buried up to their necks in |
117 |
sand? Not enough sand. |