Re: rpm fails depedency even when they're met

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

 





On Jan 7, 2008 4:40 PM, seth vidal <skvidal@xxxxxxxxxxxxxxxxx> wrote:

On Mon, 2008-01-07 at 13:39 -0800, Isabelle Poueriet wrote:
> Hello!
>
> I try to install package X that depends on shared lib Y.so.s1.
> Y.so.1 is on /usr/lib/ and it is supplied by a non-rpm package.
>
> What can I do so that rpm does not fail depedency of Y.so.1 for
> Package X?
>
> Thanks much in advance!
>
>

have the package installed by rpm. rpm doesn't look at the local
filesystem for what is or is not there. It only looks at the rpm
database. If the file isn't installed by rpm then rpm won't be able to
know about it.

Actually rpm-5.0 has a runtime probe dependency to solve exactly
this type of problem of mixing package and unpackaged libraries:

    Requires: soname(/path/to/library) = Y.so.s1

if you want a solution in packaging.

There are several other means to supply sonames-not-from-packages
to rpmlib as well, including
    mkdir -p /etc/rpm/sysinfo
    echo "Y.so.s1" >> /etc/rpm/sysinfo/Providename

hth

73 de Jeff

73 de Jeff 
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/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