- Issue created by @phenaproxima
This issue is for 2.1.x only.
With Package Manager a core module on a (slow-moving, but steady) path to stability, why doesn't Project Browser just depend on it outright, as a hard dependency, rather than a soft one?
If you install Drupal and Project Browser, with the intent of using it to install modules, you will not be able to do it unless you also know that you have to install Package Manager -- which, by the way, cannot be enabled in the UI right now without changing a setting (which is a developer task) -- and you have to configure a Project Browser setting to enable it.
What's the point of all this friction? What does it get us besides frustrating the >90% use case of people who want to use Project Browser to install modules and recipes?
This may have made sense when Package Manager was a submodule of Automatic Updates, under heavy development. But it's a core module with a beta-stability API. We should revisit this.
Add a hard dependency on Package Manager, with an update path that enables it if it's not already.
Active
2.1
Code