Which is why I said "Assuming you know your software is going into /usr." Otherwise, you can use:
find / instead of: find /usr My post was meant to be a starting point for research, not a perfect solution. -- Thomas Cameron, RHCE, CNE, MCSE, MCT Assistant Vice President Linux Design and Engineering Bank of America (972) 997-9641 The opinions expressed in this message are mine alone and do not necessarily reflect the opinions of my employer, Bank of America. > -----Original Message----- > From: Hall, Ken (IDS ECCS) [mailto:[EMAIL PROTECTED] > Sent: Friday, February 27, 2004 7:12 AM > To: [EMAIL PROTECTED] > Subject: Re: RPM question > > > Many of these products spray files over lots of directories, > not just /usr. The lowly nss_ldap, for example, puts it's > shared library in /lib, but puts a symlink in /usr/lib. Doc > files go in the > usual places, and there are manual pages, etc. When I first > started making RPM's, I used to miss files all over the place > when the product was complex. > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > > Cameron, Thomas > > Sent: Friday, February 27, 2004 12:16 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [LINUX-390] RPM question > > > > > > > -----Original Message----- > > > From: David Boyes [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, February 26, 2004 10:07 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: RPM question > > > > > > > > > On Thursday 26 February 2004 22:27, Cameron, Thomas wrote: > > > > > 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. > > > > What is wrong with: > > > > > > > > rpm -qilp [package].rpm > > > > It will tell you every file in the package and where it > > > gets installed. > > > > > > Nothing, except it's the other side of the problem. Ken's > > > creating his own > > > RPMs. You're finding out what is inside of a pre-created RPM. > > > > > > Ken's suggestion lets you start by taking a baseline of your > > > system, doing > > > your install, and then using tripwire to tell you everything > > > you did to the > > > system by comparing the current state against the baseline > > > you took before > > > starting the install. > > > > My mistake - I didn't read closely enough. > > > > I also use find and grep a lot for this kind of thing. > > Assuming you know your software is going into /usr, you could > > do something like this: > > > > find /usr > before > > ./configure ; make ; make install > > find /usr > after > > > > for i in `cat before`; do > > grep -v $i after > zzz > > mv zzz after > > done > > > > The remaining "after" file will only have those files which > > were not in "before." > > > > -- > > Thomas Cameron, RHCE, CNE, MCSE, MCT > > Assistant Vice President > > Linux Design and Engineering > > Bank of America > > (972) 997-9641 > > > > The opinions expressed in this message are mine alone and do > > not necessarily reflect the opinions of my employer, Bank > of America. > > > > ============================================================== > ================ > > 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/> > > ============================================================== > ================ >
