>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3574658. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) Related to !815 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>A long time ago, we added an empty <code>themes</code> array to the installer's info file, in the hopes that we could prevent Stark from being installed.</p> <p>This has proven to be a bad idea. There are bugs in core that basically expect Stark to exist, or sites can break during installation (and even when config actions run). It leads us to workarounds like <a href="https://git.drupalcode.org/project/drupal_cms_site_template_base/-/blob/1.x/recipe.yml?ref_type=heads#L52">https://git.drupalcode.org/project/drupal_cms_site_template_base/-/blob/1.x/recipe.yml?ref_type=heads#L52</a>, which really shouldn't be necessary.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Resign ourselves to reality and allow the installer to do what it wants to do by default, which is install Stark. It's cruft, yes, but it also won't break recipes (by default, anyway) and require workarounds on behalf of people who create site templates for Drupal CMS.</p>