1 |
Mark Knecht <markknecht@×××××.com> skribis: |
2 |
> In my case I've been slowly converting my machine back to nearly |
3 |
> 100% stable. I don't need anything more than that in my daily work |
4 |
> these days and would greatly prefer fewer updates. In the old days |
5 |
> when I ran a lot of Gentoo pro-audio overlay stuff I stay to stay |
6 |
> leading edge all the time but these days I don't do that and life |
7 |
> should be easier. |
8 |
|
9 |
A few years ago I proved it is possible to go from ~amd64 to amd64 but |
10 |
often I bump something to ~amd64 to overcome problems. |
11 |
|
12 |
(For instance it turned out libav was being pulled in because the |
13 |
~amd64 version of ffmpeg I had allowed was no longer in portage. I had |
14 |
to bump the version.) |
15 |
|
16 |
> I was thinking back about my 32-bit usage when I built the machine. |
17 |
> In those days (and it's likely still true) to run Windows VST plugins |
18 |
> you had to have 32-bit support. I was doing a lot of software synth |
19 |
> stuff a decade ago and suspect that was my main need in that area. I |
20 |
> don't intentionally use 32-bit for anything so likely I don't need it |
21 |
> at all as per Frank's comment but I also didn't feel like I really |
22 |
> wanted to deal with that right now. |
23 |
|
24 |
The processor is made to handle 32-bit so better to have it than not, |
25 |
from my point of view. (The whole multilib thing might have gone |
26 |
smoothly years ago, and with nomultilib a trivial difference, if we |
27 |
merely had had the sense to stick with Gentoo’s original filesystem |
28 |
layout for libraries. But this is my view in retrospect. We sometimes |
29 |
pay a big price for following the leads of other distros.) |