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.
Yeah, that's the general idea. Reading in the command list and options from drush.composer.xml means that we don't have to manually update them whenever they change. Just run a drush composer list --xml > drush.composer.xml every once in a while.
Having it generate it if it's not currently available is an interesting idea. Committing it directly to the repository seems the easiest to ensure it's readily available. For now, maybe we have it in the repository, and then later on evaluate auto-generating it when it's not available. Neat idea, Grayside :-) .
Comments
Comment #1
RobLoachComment #2
Grayside CreditAttribution: Grayside commentedAre you intending the `drush.composer.xml` file to be committed to the repository or run manually?
Another possibility is to make it automatic, e.g., after `drush dl` completes, after `drush composer selfupdate` is run.
Comment #3
RobLoachYeah, that's the general idea. Reading in the command list and options from drush.composer.xml means that we don't have to manually update them whenever they change. Just run a
drush composer list --xml > drush.composer.xml
every once in a while.Having it generate it if it's not currently available is an interesting idea. Committing it directly to the repository seems the easiest to ensure it's readily available. For now, maybe we have it in the repository, and then later on evaluate auto-generating it when it's not available. Neat idea, Grayside :-) .
Comment #4
RobLoach