Solved make config-recursive doesn't adapt dependencies to choices

[lib13]

Following the last post of today, I decided to start all over again.
So, first, at databases/luadbi

make rmconfig-recursive
make clean

Now, there's two ways to do this.

A)

make config

lua52-luadbi (mysql option is deselected, and postgresql is selected)

make config-recursive

the following dialogs show up:
pkg (deselect docs)
gmake (keep NLS)
gettext-runtime (deselect docs)
postgresql13-client
(...)
and so on.

This way seems correct.

B) Now, after removing previous configs, still, at databases/luadbi

make rmconfig-recursive
make clean
make config-recursive

lua52-luadbi (mysql option is deselected, and postgresql is selected)

the following dialogs show up:
pkg (deselect docs)
gmake (keep NLS)
gettext-runtime (deselect docs)
mysql57-client


So, using config-recursive as the first config command, at the top package doesn't work as intended by me.

Is this behavior a feature? Or is not working correctly?

 

[SirDice]

Is this behavior a feature? Or is not working correctly?

It's working correctly. You have to run make config-recursive a couple of times until everything has been set. The dependency chain doesn't change dynamically if you enable or disable options. The dependency chain is calculated based on the options that are set at that moment, not while you are setting them.

 

[astyle]

I actually don't like make config-recursive. IMHO, it overdoes on automation, and makes it difficult to track down compilation errors. I tried to do a "dry run" on make config-recursive, and discovered that it's not what I want it to do. Besides, I have a tendency to specify as many options as I can. That did lead to circular dependencies, but fortunately I was able to resolve that.

 

[lib13]

My conclusion is that make config-recursive is only good when there's no changes of the default options, at least for me.
Thank you SirDice and astyle.