The application I'm packaging is written in Perl, and therefore depends on a number of Perl modules.<br>The RPM build successfully detects all dependencies automatically (except for the ones defined<br>inside eval() statements). I have some inside evals so that my code will 'do the right thing'<br>
when executed on MS Windows versus Unix (These typically entail disabling features that can't<br>be supported on Windows.)<br><br>Now I'm finding that I would like to have these dependencies (that I have inside eval()s)<br>
to be included during the installation of the RPM during the yum dependency resolution<br>process. But I know on some distributions (like RHEL) I might not be able to find a package<br>(like Chart::Lines), but it _is_ available on Fedora.<br>
<br>Because these dependencies are inside eval()s, I do have to manually define the <br>'Requires' statement, but...<br><br>Is there anything that I can define in my spec file that would make yum 'try' to resolve<br>
the dependency, but silently fail if it was not found? Ie. a directive like 'NotMandatoryToRequire'<br><br>Ie. Resolve/fetch Chart::Lines when its _is_ available, but be silent about if it _isn't_ available.<br>
<br>Suggestions?<br>TIA<br>Fulko<br><br>