Yak and manifest.yml questions

[victorlin (Yu Chieh (Victor) Lin)]

Hi All,
I’m developing a grasshopper plug in using the Grasshopper templates for v6, and I wish to push it to Yak, but the I’ve ran into some problems.

What I want to know is:

1. where should I put the values for the non-required attributes in my VS project to auto populate the yml file when using the spec command?
2. when pushed, why is my plugin only showing in Rhino 6’s package manager and not rhino 7? How do I push it so it shows up in both versions.

I’ve read:

The Package Manifest

and

Yak Manifest.yml

I’m attempting to package a plugin. After using the yak.exe command ‘spec’, a manifest file is created with a yaml setting called secret, with a guid style id. secret: id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx What is this? Do I need this? What secret should be stored in a manifest yaml? The documentation about the package manifest is not very clear on what this is.

it seems that spec reads GH_AssemblyInfo data, but only the Required Attributes, can is also read the following somehow?

• URL
• Keywords
• Icon URL

I’ve tried to define fields in (ComponentNae)Info.cs, but they were ignored.

[arendvw]

@victorlin

What I want to know is:

1. where should I put the values for the non-required attributes in my VS project to auto populate the yml file when using the spec command?

As far as I know the spec command is only meant to be used once, not to update both files, or keep them in sync. For clipper I use this powershell script to keep things in sync, and automatically build a yak package (and a zip file).

@victorlin

2. when pushed, why is my plugin only showing in Rhino 6’s package manager and not rhino 7? How do I push it so it shows up in both versions.

I encountered the same issue

@will

I’d suggest either renaming the Rhino version part of the filename to support Rhino 6, e.g. ScriptParasite-1.0.4-rh6_0-any.yak , or you could mark it as being compatible with any version of Rhino, e.g. ScriptParasite-1.0.4-any-any.yak .