Hello,
I have similar concerns. Here is our problem. We have packages that
we want to install packages on NFS-mounted partitions. If we install
in the usual way, the rpm database in /var/lib/rpm gets updated.
To make queries about this NFS-mounted package, you have to goto the
machine on which the install took place to do the query because /var/lib/rpm
is local.
What would be nice is to have an rpm database on an NFS-mounted partition
and into which NFS installs would be reported.
So, I decided to try an experiment :
1. mkdir /home/scarney/package/rpm
2. rpm --initdb --dbpath /home/scarney/package/rpm
So far, so good.
3. cd /home/scarney/package/EnsiteNetworkPE/piu_emulator.59_2004_07_14_14_58_BL_c241/
rpm --upgrade --dbpath /home/scarney/package/rpm EnsiteNetworkPE.rpm
and it comes back with :
D: Requires: /bin/sh NO
D: package EnsiteNetworkPE-200407141458-0 require not satisfied: /bin/sh
D: Requires: R /bin/sh NO (cached)
D: package EnsiteNetworkPE-200407141458-0 require not satisfied: /bin/sh
D: Requires: R /bin/sh NO (cached)
D: package EnsiteNetworkPE-200407141458-0 require not satisfied: /bin/sh
D: Requires: R /bin/sh NO (cached)
D: package EnsiteNetworkPE-200407141458-0 require not satisfied: /bin/sh
which is the same problem being discussed here.
Now, I could go ahead and create the virtual package. However, that information
is alreay in the database in /var/lib/rpm and if the OS changes, they are now
out of sync.
So what I propose is perhaps to have a datbase search path when it comes to
dealing with these matters. Maybe we have a site option that says this
is the order in which you search the databases to find if something is
provided.
How hard would this be?
Regards,
Sandra Carney
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
