On Thursday 17 January 2008 16:55, Karl Larsen wrote: > Craig White wrote: > > On Thu, 2008-01-17 at 07:06 -0700, Karl Larsen wrote: > >> Michael Schwendt wrote: > >>> On 17/01/2008, Jim Cornette <fc-cornette@xxxxxxxxxxxxxx> wrote: > >>>> [...] about --force, it sounds less deadly > >>>> than using --nodeps. > >>> > >>> But --force includes --replacefiles which *is* deadly in several > >>> circumstances and hardly ever needed, because what it can do is this: > >>> > >>> --replacefiles > >>> Install the packages even if they replace files from > >>> other, already installed, packages. > >>> > >>> Using --replacepkgs or perhaps --replacepkgs --oldpackage is [more > >>> than] enough, usually. > >> > >> I have used --nodeps and --force in a few cases which have nothing > >> to do with removing pulseaudio. The meaning of Safe removal of > >> pulseaudio is that you do NOT do anything but rpm -e. If you get > >> dependancies you rpm -e those first. Nigel likes to use yum remove but I > >> am gun shy of that now :-) > > > > ---- > > as long as you remain oblivious to the fact that you really don't know > > what you're talking about, I would suppose that makes sense. > > > > The fact is, the methodology you have chosen, those packages you removed > > will return the next time one of the remaining packages is updated. > > > > Craig > > Exactly. I have one pulseaudio update waiting now. I do not want it > to update. How do I stop the update? > > Karl Allowing the update should not cause any problems. Re my reply to your reply offlist. As long as alsa-plugins-pulseaudio is removed, thus disabling pulseaudio, this pulseaudio update should do no harm. Nigel.
