On 2/22/20 8:01 PM, Ken Moffat via blfs-support wrote:
On Sat, Feb 22, 2020 at 04:28:31PM -0500, Scott Andrews via blfs-support wrote:
On 2/22/20 1:56 PM, Ken Moffat via blfs-support wrote:
Any suggestions for taming pulse, please ?
This is why I don't use pulseaudio. It is not needed alsa in sufficent.
Except that the firefox devs prefer to use pulse (to limit their
variations, I think) so for BLFS we prefer to keep close to that.
I suggest make uninstall. Or in my case rpm -e pulseaudio.
And that isn't taming it, is it ? - it's nuking it.
I do happen to know what got installed by pulse, but after that many
other packages have been built so just ripping it out (even if that
turned out to be the best approach) can break other things which
link to pulse. Also, 'make uninstall' is usually the least-tested
option of any Makefile.
ĸen
You are making the case for a package manager.........
Which rpm will tell me what needs rebuilt, I can also just
configure/rebuild just pulse audio and reinstall when I have a handle on
the issue. It looks like you are stuck with rebuilding the entire
system to fix on package. Again that is why I use a package manager, as
it lets me reuse, change and restart my builds at any point without
always started from the beginning . And if something breaks then I can
fix the breakage. At the point that I am at with my build I have
files/data of what each package contains, what it needs/requires and
what it provides as dependencies and what are other packages that link
to it . That lets me decide upon a proper course of action. In your
case for example if the latest version of pulse is the problem all I
would need to do is build and install the previous version ( provided
the shared libs version stayed the same) and I have the issue resolved.
I don't see why LFS/BLFS has an ad-version to package managers, I don't
see the value in that as there are many good benefits and almost zero
detriments.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
