I recently came across this change record for D8: https://www.drupal.org/node/2952947
What this has done in short is that it has allowed installation profiles to specify install
dependencies in addition to the preexisting dependencies
. D8 uses .yml files, but here's how that could look in .info files:
name = Standard
description = Install with commonly used features pre-configured.
version = BACKDROP_VERSION
backdrop = 1.x
install[] = admin_bar
install[] = ckeditor
install[] = comment
install[] = dblog
install[] = views_ui
install[] = update
dependencies[] = node
dependencies[] = block
dependencies[] = color
dependencies[] = config
dependencies[] = contextual
...
The dependencies
array would be treated as a set of "hard" dependencies, meaning that they cannot be uninstalled, because the profile depends on them. If the profile simply wants to specify a list of modules to install, but upon which it does not actually depend, it can use the install
array.
To maintain backwards compatibility, profiles which only define a dependencies
array, but not an install
array, would have their list of dependencies treated like an install
list. This backwards compatibility layer could be removed in Backdrop 2.0, which should allow enough time for profile authors to separate their install
list from their actual dependencies.
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface