Re: finding requires

[Tim Mooney <mooney dogbert cc ndsu NoDak edu>]

In regard to: finding requires, Cameron Scott ICM N MC MI SI 6 said (at...:

>When I build my package, one of the Requires entries is a local path to
>tcl-tk.
>I've looked in each of the files in my files list to see if they have a
>shebang or something but grep produces no output with this path.
>I don't know where this is coming from!

The thing I've done in situations like this is do the

	rpm -v -bi whatever.spec

to get the files installed (preferrably into a BuildRoot).  Once the files
are prepared, cd into the buildroot directory, e.g. /var/tmp/foo.  You
probably also have a prefix under the buildroot, such as /usr/local or
/opt/foo . cd down into there.

>From that point, use find and the process of elimination to figure what
subdirectory contains the file(s) that are generating the dependency.  One
way would be:

for d in *
do
  echo "$d"
  echo '----'
  find $d -print | /path/to/find-requires | grep -v 'the-odd-dependency-here'
done

That should first tell you what directory find will search through,
and then only generate output if grep finds a matching regex in the
output from find-requires.  Then just cd into that directory, and repeat
the process until you've narrowed your search enough to find the file(s)
in question.

Tim
-- 
Tim Mooney                              mooney@dogbert.cc.ndsu.NoDak.edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164