| 1 |
On 2022-07-15, Julien Roy <julien@××××.ca> wrote: |
| 2 |
|
| 3 |
> One of the side effects of using proprietary software : you can't |
| 4 |
> control with which flags it gets built. |
| 5 |
|
| 6 |
Yep. I didn't used to have the chrome binary package installed, but |
| 7 |
there are a couple things that I've never gotten to work in Chromium |
| 8 |
(e.g. Webex). |
| 9 |
|
| 10 |
> With chromium-bin, there is a wayland USE flag, but nothing for |
| 11 |
> jack. |
| 12 |
|
| 13 |
I looked into that more, and I had misread the emerge output. It |
| 14 |
wasn't google-chrome that depended on jack, and now I can't figure out |
| 15 |
why it was installed. I did |
| 16 |
|
| 17 |
# emerge -C virtual/jack media-sound/jack-audio-connection-kit |
| 18 |
# emerge -auvND world |
| 19 |
|
| 20 |
It didn't get reinstalled. And then a subsequenct |
| 21 |
|
| 22 |
# emerge --depclean --ask |
| 23 |
|
| 24 |
removed another half-dozen audio-related packagets (zita-* and |
| 25 |
realtime-*, whatever they are). I'm sure the next time I try to use |
| 26 |
audio on that machine it won't work. |
| 27 |
|
| 28 |
I used to think that someday Linux sound support would get |
| 29 |
straightened out, but it just keeps getting worse... |
| 30 |
|
| 31 |
-- |
| 32 |
Grant |
Archives