Description of problem:

The spec file now creates a /tmp/myrequires in the core of the spec
file.  The right way (or at least a better way) to do this is to
include the file, say gfs-requires, as Source1 and %define
__find_requires %{SOURCE1} (it might be that the %define should be
after the Source1, I don't know for sure).

The problem with /tmp/my_requires is that builds might conflict w.r.t.
ownership etc.  The simple example I saw was a -bs done as root
followed by a --rebuild done as a normal user, which caused errors
because the file was owned by root.  If more packages would use a
similar method, this would even cause everything being screwed up.

Version-Release number of selected component (if applicable):
6.0.0-15