|Issue tags:||installation profiles|
One of the major problems with install profiles, is that they do not have access to the Drupal API, and are _only_ loaded during install.
This results in almost every install profile having to write their own custom contrib module, to do the actual work the install profile aims to do.
a) always loading the install profile code
b) adding the install profile namespace to the bottom of module_listing
This will give install profiles access to the full Drupal API, and work towards removing the differences between install profiles and modules.
Install profiles thus become a superset of the Drupal API and not a subset, and you have to jump through fewer hoops to write install profiles.