Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We need a D7 install profile in the D7 branch, which we kinda have already, but we currently need provision to install it, this should not be the case, we should be able to install the profile without provision, so people can help with the port without needing to install a full Aegir stack, or so we can test it using simpletest or something.
This issue I need to do I think.
Comments
Comment #1
Steven Jones CreditAttribution: Steven Jones commentedTurns out I actually did this a long while ago, so this one is done!
Comment #2
ergonlogicLast week, I started looking into seth.vincent's work to port hostmaster.profile to use the Profiler library. I'm very interested in getting this working in the 2.x branches, since I'd love to be able to make a sub-profile that inherits from hostmaster, and then extends it with uc_hosting, etc. If I understand how Profiler sub-profiles works, we should be able to selectively include and override install tasks. This should make a testing/development frontend-only profile easier to implement and maintain.
Assuming a dependency on the profiler library is acceptable, I'd be happy to undertake this task right away.
Comment #3
Steven Jones CreditAttribution: Steven Jones commentedI don't have any problems with this in principle, but we don't even know what we need from our D7 installer yet, so it may be a bit premature to get it working in Profiler if we're going to find in six months we need to re-do it again.
Comment #4
ergonlogicI posted #1463128: Use the Profiler library in hostmaster.profile to follow-up, so I'll close this issue again.