trying to understand the --no-exec activate option (on by default?)

[René J.V. Bertin]

Hi,

I'm trying to understand how/where the activate --no-exec option is set, I have the impression it's on by default.

For instance, I have a port that implements the following approximation of a "strongly suggested runtime dependency":

```
        # we cannot use depends_run because of circular dependencies so we can
        # only emit a warning if we don't detect kf5-kdevelop-clang-parser as active
        # in the post-activate. This warning will always print at least once...
        post-activate {
            if {[catch {set installed [lindex [registry_active ${name}-${PARSER}] 0]}]} {
                ui_warn "Please remember to install (or activate) port:${name}-${PARSER}"
            }
        }
```

That warning only prints during an install or upgrade (when the runtime dep is not active).

The default for this option should be OFF IMHO; there are also ports which do important things in the post-activate; the lldb ports remind the user that an executable needs to be code-signed for instance. Evidently this has to be done each time the port is (re)activated.

R.