In regard to: Should %doc files be checked for dependencies?, Simon Mudd...:
I'm trying to package some example documentation/configuration files
for the Postfix MTA. Some of the examples include perl scripts,
including perl scripts which themselves use perl modules.
These documentation files/directories are tagged as %doc in the file
list, are not in /usr/bin or any "binary" directory) but find-requires
appears to be including these dependencies into the rpm.
This I don't want as there are no DB_File rpms for my target
platform(s) including Enterprise Linux, and in any case these
"dependencies" are not in any of the run-time scripts.
IIRC there is no way to explicitly avoid a specific RPM generated
dependency, disable all dependency checking. AFAICS the only solution
is to write my own find-requires (or find-requires wrapper) which avoids the
generation of the unwanted perl(DB_File) dependency. Both alternatives
appear to be rather unclean.
Am I missing an easier way of avoiding this unwanted dependency?
The normal way to accomplish this is to remove all execute permission
from example/doc scripts after they're installed into the buildroot.
I haven't verified whether that will work with perl dependencies, but
that's the first thing I would try.
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
