clean generated theme depends on collective.themesitesetup

[fredvd]

Why is a generated barcelonata theme in a new add'on by bobtemplates automatically adding a dependency on collective.themesitesetup? It errors for me because the dependency is not pinned, it might also for others using the unified installer, I hope allow-picked-versions is set to false there as well.

Isn't it better to keep the generated theme scaffold as minimal as possible and stick to core Plone packages?

And especially this add'on is a bit strange, because it adds GS install/uninstall support from the manifest.cfg so you can upload zip files. But the add'on was just scaffolded as a filesystem theme, so generic setup can be added to the add'on.

edit: and there are two more, plone.app.themingplugins and collective.themefragements. If these are defacto useful and general in use add'ons, maybe we can add pinnings for them to ecosystem in coredev?

[balavec]

I was also testing this addon and will prepare a PR.

[balavec]

I pushed PR: https://github.com/plone/bobtemplates.plone/pull/414