- Issue created by @heddn
- Status changed to Closed: works as designed
7 months ago 11:18pm 29 May 2024 - 🇺🇸United States drumm NY, US
Modules & themes were included.
Distributions currently don’t have a great way to check compatibility. Since we aren’t serving them via packages.drupal.org, we do not have this sort of metadata in our DB.
Since going off drush make packaging, distribution support is somewhat undefined. Currently, any distribution still listed as a distribution is either not maintained, or has a special installation process. Distributions on Drupal.org can’t be installed via Composer via any well-defined process.
Many distributions have moved to general projects. A general project with a release and a valid composer.json is installable via Packagist.org. We also don’t keep compatibility metadata on-hand, since Packagist.org handles that. Compatibility checking is possible, but not practical. Some are templates and would be set up with
composer create-project, some are dependencies that would be set up withcomposer require. Then would have to see if the composer command succeeded and/or see what happened incomposer.lock. Even if we automated all of that, I fully expect enough edge cases to cause problems.