On Fri, 2007-02-23 at 14:22 -0500, Ric Moore wrote: > On Fri, 2007-02-23 at 10:21 -0500, Don Levey wrote: > > > In another message someone suggested reading the current RPM database > > before an reinstallation upgrade and making sure to install those > > packages. That would eliminate a goodly amount of time from my upgrade > > procedures, and a tremendous amount of pain. Ideally something would > > detect my configurations for those programs and save them out somewhere, > > but I'm not holding my breath. > > I think it might be wise to consider the old Caldera notion of > using /opt to contain all the goodies that you post install and wish to > be left alone. Then you merely fresh install the core apps while > leaving /opt (and /home /root) alone. It's worth a thought. Ric > > -- That makes sense (assuming that /opt is a separate partition...). What I'm thinking of, though, are RPMs that I've pulled off of official repositories and installed, ones that aren't in the list of packages presented during an install. Come to think of it, even if they *were* presented during installation, that wouldn't be as useful as I'd still need to go through the list to pick and choose. What if... there were a way of going through the RPM database, creating a list, and presenting that to some sort of kickstart routine? -Don
