Hi,
This is probably seen as a forbidden hack, but is there a way to access
variables from the macports namespace in a PortGroup (or Portfile)?
I know that "user" code like this is executed under/through `mportopen` which
is in that namespace, but when I invoke `namespace children` I only see
FWIW, I'm now using `port archive` in my "devport" PortGroup, so that updating
the main port and the companion devport with developer content doesn't
re-activate that content if the user deactivated it. (It still gets installed
normally otherwise.)
R.
On Monday October 23 2023 01:34:03 Eric Gallager wrote:
>I sometimes try using the `port archive` command, and one thing I'm
>wondering about it is, why does it bother calculating conflicts if it
>doesn't actually install the port?
That's strange, in my experience conflicts are detected when
