It seems potentially useful to allow install profiles to be run, not only at site creation, but also at any point afterwards. That would make them useful for publishing "recipes" which would mostly involve the creation of site building items such as content types, views, and fields. However, they could also be used to install contrib modules, themes, and layouts where necessary.
This would allow users to use a install profile even after they have installed backdrop and otherwise started building their sites. And it would allow them to run more than one install profile, each of which would provide a different set of functionality.
Recent comments
I'm glad you've found it quite useful too! I'm curious to know why you'd like to unpublish some of your modules or themes? They're not ready or are they more personal projects? I can help...
My work and a big thanks to all of you
Slight improvement to @argiepiano's procedure. Again for PR 4690, it would be: Using shell access, go to the Backdrop doc root. Run this command to get the diff file...
Workflow for core update with fixes that are not yet in core
This issue is seeing some progress, but there are some questions that might benefit from a UX discussion. https://github.com/backdrop/backdrop-issues/issues/2894
Apr 18th Weekly Meetings