In regard to: How to populate RPM db with empty entries, Albert Chin said...:
using a fresh RPM database (rpm --initdb), we get errors like so:
error: cannot open Basenames index using db3 - No such file or directory (2) error: cannot open Dirnames index using db3 - No such file or directory (2) error: cannot open Filemd5s index using db3 - No such file or directory (2)
We usually provide a stub package that provides /bin/sh for our RPM postinstall scripts:
Note the absence of the "Basenames", "Dirnames", and "Filemd5s" files, presumably because our stub package contains _no_ files (it's sole purpose is to Provides: /bin/sh). Is it possible to create all files used by RPM at --initdb time or when our stub TWWos package is installed? I found %ghost at http://rpm-devel.colug.net/max-rpm/s1-rpm-inside-files-list-directives.html but that doesn't really help because we don't want any files associated with our TWWos stub package.
I don't know the answer to that, but it occurs to me that your TWWos package could include your directories (/opt/TWW and children, relocatable if you allow that). If you're adamant about not having anything but Provides in TWWos, do you require any other packages (something like a TWWbase that contains any support scripts or READMEs/docs you use)?
Tim -- Tim Mooney mooney@xxxxxxxxxxxxxxxxxxxxxxxxx Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
