Manifests files... some details about it

Development
1

Hi, i would like to get clear the use of json manifests …

what must be done ?
is there one for each module ?
is the main manifest (for the slug) is important and why ?
in the future, will we have to do the same, vcv 1.0 ?

thanks to enlight me on this :slight_smile:

2

vcv 1.0 plugins should have a manifest. There are details if you follow the links in this post

It’s one file for the whole plugin, it has sections for each module.

I’m not sure where things are with v0.6.

3

AFAIK manifests in 0.6 just tell the update system what version everything is and where to find it. And most of that is presently managed by the build team outside of initial setup.

4

But at final, for 0.6x , should i do 1 manifest for my slug, or it is not necessary ?

5

I don’t believe you need to include a manifest file in your build for 0.6x.

For adding your 0.6.x plugin to the plugin manager, follow the section called Adding your plugin to the VCV Plugin Manager in here…

1 Like
6

It looks like the JSON schema for 1.0 manifest files changed recently. Modules is now an array, it used to be an object. Anything we should know about this?

7

No, other than that “modules” is now an array instead of an object.

2 Likes
8

Is there a handy specification for the manifest file? For those of us on platforms where python3 isn’t working.

9

Not yet, but you can use https://github.com/VCVRack/library/tree/v1/manifests for examples.

1 Like
10

I had some problems on Debian Linux, because the required Python version was not in the package system. But I could install it easily by following this answer here:


I even installed the latest Python 3.7.3 version, works with the VCV Rack scripts.

1 Like