I may have asked about this before without getting any good answers, but
something I've wondered about for a long time, is whether I can Provide:
something "privately". That is, can I say that some package A provdes
e.g. libA.so.1, but only for the use of package B? I mean, so that if
package B has
Requires: libA.so.1
then "rpm -i B-1.0-1.rpm A-1.0-1.rpm" will install packages without any
problems on a system where libA.so.1 is missing, but for a package C
with the same "Requires", rpm -i C-1.0-1.rpm A-1.0-1.rpm will fail with
dependency error (that is, C does not "see" the provides of A-1.0-1.rpm.)
I want this because I am packaging my own copies of 3rd party
("non-core") libs as suggested by
https://www.redhat.com/f/pdf/rhel4/AppCompat.pdf, and
1. I want to have this libs in a (sub) package separate from the
actual application rpm.
2. I would like to be able to install the application rpm without
this special sub package if the libs are already installed
globally on the system.
(Note that the library package can't install the libs on a "normal" lib
directory as that could easily lead to file conflicts. Instead, the libs
are written to an a special directory configured as an additional place
to look for shared objects, in the application binary.)
Actually, it's also because of this situation I've wanted "or" in
Requires (see another recent thread), as that would present an
alternative solution to the problem.)
- Toralf
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
