With the addition of info files and install hooks to installation profiles, they gain a status equivalent to that of modules and themes. However, in order to make an installation profile available, unlike modules or themes, it must apparently be added to the
profiles/ folder in the code-base itself.
This may work (more or less) when the profile and code-base are distributed together as a third-party package, but if eg. a profile is supposed to be downloaded by itself or created by the local web admin, we want it to be outside the code base, for the same reason as other addons. That's exactly what
sites/[conf_path] is for.
I propose that install_find_profiles() be extended to use the same search pattern as module and theme discovery, looking in
./sites/[conf_path]/profiles/ (in order of increasing priority, to allow overrides).
|PASSED: [[SimpleTest]]: [MySQL] 39,799 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 37,109 pass(es).|
|FAILED: [[SimpleTest]]: [MySQL] 18,877 pass(es), 298 fail(s), and 296 exception(s).|