poudriere options: -c flag explanation

[abi]

On 04.03.2018 02:26, Le Baron d’Merde wrote:
> On Sat, Mar 03, 2018 at 01:02:23PM +0300, abi wrote:
>> Hello,
>>
>> Assuming that -n flag suggests that options run recursivly for deps chain,
>> isn't  -c flag should always invoke dialog4ports for every port with options ?
>>
>> For example, poudriere options -c editors/libreoffice asks for options
>> through all dep chain if runs the first time, on subsequent run it asks for
>> options only for original port or if it find no cached options.
>>
>> This looks confusing, is it intended?
> The default behavior of ports-mgmt/poudriere is to open the dialog to set OPTIONS
> for each selected port (targets) and all its dependencies, unless they were
> already set.
>
> Issuing 'poudriere options -n' will just open the dialog to the target(s) and not its
> dependencies. Again, but for those which already have OPTIONS set.
>
> The -c flag in 'poudriere options' delete the previous selected options to the
> specified target(s) and open the dialog to set them again - what may include
> dependencies without OPTINOS set already.
>
Isn't this behaviour incorrect? If -c skips dependencies with OPTIONS, 
it is impossible to revisit them? For example, if I want to re-think all 
dependencies of java and check their options, how can I do this? Man 
suggests that -c behaviour is recursive (if -n is not provided).