Re: 'Requires' directive in spec file ignored?

In regard to: Re: 'Requires' directive in spec file ignored?, Brian...:

> On Mon, Apr 07, 2008 at 01:00:11PM -0400, Jeff Johnson wrote:
>> Basically same as doing
>>     %define version %{version}
>> which can never be evaluated.
>
> I supply the macro in an external file, so I don't see that complaint.
>
>> After commenting out all the elements in, I see dependencies:
>
> And I don't:
>
> rpm -q --requires -p mDNSResponder-107.6-2.i386.rpm
> /bin/sh
> /bin/sh
> /bin/sh
> /bin/sh
> libc.so.6
> libc.so.6(GLIBC_2.0)
> libc.so.6(GLIBC_2.1)
> libc.so.6(GLIBC_2.1.3)
> libc.so.6(GLIBC_2.2)
> libc.so.6(GLIBC_2.3)
> libdns_sd.so
> libpthread.so.0
> libpthread.so.0(GLIBC_2.0)
> libpthread.so.0(GLIBC_2.1)
> rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1

Assuming rpm is using executabledeps.sh to actually generate the
dependencies in the executable() namespace, then the first version of
"bash" in your PATH must support the --rpm-requires hack.  Does your
version of bash support that?

Tim
-- 
Tim Mooney                              [email protected]
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164