vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| |||
| wong_powah@yahoo.ca wrote: > I created a rpm (.spec file) to install a program and create a > symbolic link to it. After I do "rpm -e" to remove the package, the > program and symbolic link still exist, how to fix this problem? If you have a script that creates a symbolic link on install (probably "post"), then you need to create a script that destroys it upon uninstall (probably "preun"). If -e isn't removing files "owned by" the rpm, they may be "owned by" more than one rpm or your uninstall routine may be faulty. You could always try "--force" at your own risk. |
| ||||
| On 31 Aug, 22:43, Allen Kistler <ackist...@oohay.moc> wrote: > wong_po...@yahoo.ca wrote: > > I created a rpm (.spec file) to install a program and create a > > symbolic link to it. After I do "rpm -e" to remove the package, the > > program and symbolic link still exist, how to fix this problem? > > If you have a script that creates a symbolic link on install (probably > "post"), then you need to create a script that destroys it upon > uninstall (probably "preun"). > > If -e isn't removing files "owned by" the rpm, they may be "owned by" > more than one rpm or your uninstall routine may be faulty. You could > always try "--force" at your own risk. postun: it's usually done as a postun. You can also do "rpm -q -f [filename]" to see what packages own or think they own it. And there are fascinating %config options to preserve or discard config files on removal. |