On Monday 21 May 2007 22:13, Patrick Shanahan wrote: > * Rajko M. <[EMAIL PROTECTED]> [05-21-07 22:20]: > > I don't know internals of > > rpm --rebuilddb > > but I was using it and it seems that it doesn't search hard disk for > > installed third party software. > > > > The sound driver is: > > realtek-linux-audiopack-4.05f.tar.bz2 > > and it will compile alsa driver and some XRealMixer v0.5 from sources. > > John mentioned that he removed directories, but I didn't ask which as > > installing alsa via YaST should bring sound in order. > > Using an rpm-based system requires the use of rpm packages. The use > of tar-balls will corrupt the rpm system and do not show up in the rpm > database. Tar installations can replace libraries required by your > (rpm) installed system and break things as you seem to have found with > the alsa package. Removal of tar installations and source built > installations is very difficult. > > You must be experienced and knowledgable to incorporate a mix. The > only really safe usage for the unknowning is those tar packages which > are self contained static packages which install in their own > directory and are removable by deleting that directory structure. > > If you *must* build a driver (as it appears) you should incorporate > the use of "checkinstall" which generates rpm packages for > installation after build and allows for save removal, if necessary or > desired.
Well, it's not my problem :-) I always check before using tarballs for all reasons that you listed above. John (original poster) can look in install script and see what was removed, but as you said it is not easy. That is the reason I proposed reinstallation of alsa. If that doesn't help, than he can always analyze the problem which can take more time than reinstallation of whole system, and of course next time install and use "checkinstall". -- Regards, Rajko. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
