Confused about slugs about library HOT 9 CLOSED

"Autodafe - Drum Kit" should be your slug forever and should match the manifest.

from library.

ok, but:

slug*: Unique identifier for your plugin. Should never change. Avoid spaces. Prefix with your company or developer name if you plan to release multiple plugins, e.g. "VCV-PulseMatrix". But most importantly, should never change.

So, no problems if I use spaces in the slug?

from library.

Ideally, but most importantly it should not change.

from library.

ok, so I have better change the slug in my plugins and not in the manifest

from library.

No, the C++ slug is the one you should use. Change the manifest slug to match the C++.

from library.

if I use slug "Autodafe - Drum Kit" , "make dist" doesn't work...it creates different folder one for the "-", one for "Drum" and one for "Kit"..."Autodafe" folder is skipped...

I think I had better move to a "spaceless" slug...

from library.

I can confirm that spaces in the slug are not a good idea at all...

1. i had to put SLUG ="my plugin with spaces in its name" in double quotes in order to "make dist" work, but then:
2. when Rack downloads 'my plugin with spaces in its name.zip' it probably gets a 404 error and downloads only 229 KB (the 404 page, probably), zipped and the unzip process fails.

from library.

Looks like you chose on changing the slugs. Probably better for the long run.

from library.

yes, actually if a ZIP file contains spaces in it Rack is not able to download it. Hence the change

from library.