Rhino 8 for Mac, Package Manager offers plugins incompatible with .NET 7

We are working on a yak package of our Grasshopper plugin that is compatible with Rhino 8 for Mac (i.e., that is compatible with .NET 7 on Mac). Currently, there is an issue that is blocking this, as described here.

I would prefer if incompatible versions of our plugin would not show up in the package manager of Rhino 8, however, it seems this is not possible. As an example, yak packages whose architecture is rh7_0-mac show up for Rhino 8 as well. In light of the .NET runtime change this causes problems and confuses users. Is there any intention to change this behavior of the package manager, or is there a way to work around it?

1 Like

I believe that McNeel has an open issue to allow bundling 4.8 and 7.0 in the same package so that things work on Windows regardless of which command line setting is used.

Perhaps this could be bundled into that release, such as via manifest file flags for OS and version which the package manager respects and which Rhino also checks when installing.

1 Like