I used the yak.exe (0.13.0) shipped with Rhino8 to install a package.
When the package is built using RhinoCommon 8.5, yak correctly installs it in Packages\8.0
When the package is built using RhinoCommon7.X, yak throws an error saying that No compatible distribution found for <packageName>
I was expecting Yak to either handle that and install the package under Packages\7.0 or have an option on the install command of Yak to choose Rhino version.
Hi Devang, this should be resolved in Rhino 8.6.
The yak.exe CLI tool will now allow the installation of packages created for older versions of Rhino (the same behaviour as the Package Manager in Rhino). To be clear, the package will be installed for Rhino 8!
Can I get a url to this new Yak.exe @will ? Currently, we use yak.exe from https://files.mcneel.com/yak/tools/latest/yak.exe in our CI
We can host the yak.exe ourselves but I would really like to avoid that. Getting a url from McNeel will be preferred so that we automatically get the latest version of yak.exe once it’s out.
Can you elaborate a little on how you’re using the yak CLI in your CI builds? I would expect that if you’re installing packages then you would also have Rhino installed.
I’ve logged an ticket to update the self-contained yak.exe that we host. This one is built a little differently so as not to require additional DLLs, making it easy to download!
https://mcneel.myjetbrains.com/youtrack/issue/RH-81694/Publish-a-self-contained-yak.exe-for-v8
Sure. Our CI pipeline fetches the yak.exe from https://files.mcneel.com/yak/tools/latest/yak.exe.
We have and additional script run by the software center that again uses the yak.exe to install the package to a user’s machine.
Any idea when this will be available @will?