plone.volto:default should install all necessary dependencies

[jensens]

In order to have a sane dependency graph on GenericSetup-Level, the default profile must depend on profile-Products.CMFPlone:dependencies.

Currently one need to depend on both profiles with some disadvantages:

If not:

• the order of dependency installation is fuzzy and so volto overides may not be active
• not all types are installed.
• not all features are present.

143 is probably related.

[jensens]

actually, in my profile-myproject.backend:default I need

    <dependency>profile-Products.CMFPlone:plone</dependency>
    <dependency>profile-Products.CMFPlone:dependencies</dependency>
    <dependency>profile-plone.app.contenttypes:default</dependency>
    <dependency>profile-plone.volto:multilingual</dependency>

to install a Volto site using plone.distribution with a profiles.json like so

{
  "base": [
    "myproject.backend:default"
  ]
}

I am pretty sure this is more than we want.

[davisagli]

@jensens Just to make sure I understand correctly, your goal would be that your project can depend on only profile-plone.volto:multilingual and the rest gets pulled in automatically, right?

[jensens]

This is what i would expect from a dependency tree.

[jensens]

FTR: it turns out the problem is using plone.distribution together with a custom profile. in order to make it work correctly one has to define in profiles.json:

{
  "base": [
    "Products.CMFPlone:plone",
    "Products.CMFPlone:dependencies",
    "plone.app.contenttypes:default",
    "myproject.backend:default"
  ]
}

and in the metadata.xml of the myproject.backend:default profile:

<?xml version="1.0" encoding="utf-8"?>
<metadata>
  <version>1000</version>
  <dependencies>
    <dependency>profile-plone.volto:multilingual</dependency>
  </dependencies>
</metadata>

So this is more a documentation issue of Volto together with plone.distribution.