Re: Resolving Dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 14 Jul 2011, Ramin Rad wrote:

The dependencies in RPM are only meaningful when it comes to packages (and
virtual resources) that are in the RPM DB.

If you say "Requires: libQtCore.so.4", RPM thinks there is another RPM
package called libQtCore.so.4 that has to be installed prior to this and it
checks its database and it doesn't find it, hence the error.

What you really want is file dependency. I am not sure if RPM supports that,
but you can simply put something like this in your "%pre" section:

RPM supports file dependency (for files provided by RPMs) - just use
the full path:

Requires: /usr/lib/libQtCore.so.4

###########
%pre

if [ ! -e /usr/lib/libQtCore.so.4 ]
then
  echo "ERROR: /usr/lib/libQtCore.so.4 doesn't exist! Bailing out."
  exit 1
fi

# end of %pre
###########

That works for files not provided by RPMs.

--
	      Stuart D. Gathman <stuart@xxxxxxxx>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list


[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux