I found tripwire to be useful in identifying added files when creating or updating complex RPM's. Run it before doing make/make install, and again after, and you get a list of files added and changed.
> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Alan Cox > Sent: Wednesday, February 18, 2004 4:53 PM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] RPM question > > > On Mer, 2004-02-18 at 18:15, Ranga Nathan wrote: > > On my slackware (Intel) I always used the 'configure, make, > make install' > > process. It worked flawlessly everytime. This way I always > got the latest > > software. With RPMs I have had problems and then I had to > go under the > > hood. RPM's are usually behind since there is a process to > build the RPM > > and test it. > > You can do that with RPM based distributions too, but it > turns them into > slackware rather rapidly (ie no dependancy management, no > verification, > no change control) > > The way I normally roll an updated RPM is > > Grab old SRPM > Install > Edit spec file and change versions > Add new version tar ball into sources > Try and build > > Any patches that fail check if they have been applied or if > they matter. > Adjust and/or remove > > Build > Install > ============================================================================== If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. <http://www.ml.com/email_terms/> ==============================================================================
