Quoting François Pons <[EMAIL PROTECTED]>: > Scott Chevalley <[EMAIL PROTECTED]> writes: > > > I've been updating my box using urpmi --auto-select for at least the past > two > > or three release cycles, constantly running cooker. I'm wondering if there > is > > anyway to use urpmi or rpm to give me a list of files that exist on my > system > > that don't belong to any installed packages, so I can clean things up a > little > > bit. > > > > I'm sure it would be much easier to just install from scratch, I just don't > > > feel like tracking down all the contrib and plf packages I've installed > over > > the years again. > > This could be a good tools to have, allowing unknown files to be seen, msec > is > already doing this though. > > It could be nice to rebuild broken rpm database (I suppose this is what you > want > here ?). > > François. > >
That would be a good side effect, but I'm looking for a way to find all the old junk lying around my hard drive. A few weeks ago I had a problem with styles in KDE on cooker not working or showing up, and found the problem was an old libqt library in /usr/lib/ that was messing things up. I removed it and styles started working again. I probably should just wipe everything out and do a fresh install every so often, but I'm lazy and it's so much work to track down every little package that I need to have installed to get the system back to a comfortable state. Which reminds me.. if I were to create an autoinstall disk from my current system, would it only list packages from main or would it include contrib and plf packages? If I then attempted an install from that disk would it have a problem finding all the rpms if I kept a local mirror of cooker, contrib, and plf? Just a thought... I'm probably making it more complex than it needs to be... Thanks, Scott
