Ryan Carsten Schmidt

> I am a little unclear about what issues still need to be addressed before merging it. Sorry, I haven't really looked at this again since my April comments.

> It seems obvious that this port can't be used as any kind of dependency of another port. I don't know why you say that. I created this port for...

This is caused by macOS 13 and later containing a different `patch` program (which defaults to applying a patch in reversed order when that works) than macOS 12 and earlier...

> * [x] referenced existing tickets on [Trac](https://trac.macports.org/wiki/Tickets) with full URL in commit message? You have not referenced the ticket in the commit message. We can fix it by using...

> Sorry for a delay. Looks like it actually installs correct versions. Compare existing [3.38.1](https://ports.macports.org/port/gcr/details): > > ``` > /opt/local/lib/libgck-1.0.dylib > /opt/local/lib/libgck-1.dylib > /opt/local/lib/libgcr-base-3.1.dylib > /opt/local/lib/libgcr-base-3.dylib > /opt/local/lib/libgcr-ui-3.1.dylib > /opt/local/lib/libgcr-ui-3.dylib...

> ``` > ../../src/post-config.h:11:17: warning: using directive refers to implicitly-defined namespace 'std' > using namespace std; > ^ > ``` `using namespace std;` should appear after the system `#include` directives...

In what way are this portgroup's defaults used by the ports that include it? It looks like by default the nodejs dependency will be added to depends_lib? If so, all...

The `revision` must be increased, both since you're removing a library dependency and because the installed files will change on disk (they will no longer be linked with libhdf5).

> Yes, it is still needed on macOS 14, but should be removed for macOS 13. (At least going by results of CI on either. Locally I can only check...

It looks like the same problematic condition was copy/pasted into at least the gcc-devel, gcc11, gcc12, gcc13, sundials5, and root6 portfiles.