Hi Graham,

I sure couldn't find it in plugin docs (spent significant time 
looking/digging).  If it is there somewhere, I certainly apologize, but as 
mentioned, I could not locate anything (nor could Google).

Andrew

From: Graham Leggett <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Wednesday, October 10, 2012 5:13 PM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [mojo-dev] autoreq: no

On 10 Oct 2012, at 23:20, "Crawford, Andrew" 
<[email protected]<mailto:[email protected]>> wrote:

I've been scouring the RPM Plugin documentation and Google search results, 
trying to find a way to set the value of "autoreq" to "no" in the .spec file 
that RPM-Plugin produces.  So far I have not found any way to accomplish this 
(using configuration), and wanted to ping this list to see if it's possible.

I do not have root access in my environment, but would still like to create and 
deploy custom RPM files.  To do this, I need to maintain my own "private" RPM 
database.  When the value of "autoreq" is set to "yes" in the RPM-Plugin's 
.spec file, this setup fails as it thinks things like /bin/sh are not present 
on the system.

I know I can use the "--nodeps" RPM argument, but then I cannot checks for the 
dependencies that I do want to manage (one custom RPM requiring another custom 
RPM).  The best way to get what I need would be to disable the auto dependency 
(autoreq) setting.

Please let me know if there is a configuration directive available to disable 
this setting.

Is this not covered by the plugin docs?

Regards,
Graham
--

Reply via email to