Drush make currently includes a PATCHES.txt file in the directory of any patched project. This feature would add a new command to create a single file containing all patches from a given make file.

This isn't ready to go, but is an initial work in progress, and could use tests.

One alternative approach would also be to just make this an option to the normal make command, defaulting to placing the file in a docs directory on full builds containing core.

CommentFileSizeAuthor
#2 drush-make-patches-option-1465810-02.patch2.22 KBjhedstrom
drush-make-patches-command.patch2.11 KBjhedstrom

Comments

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Title: Create a command to generate a single PATCHES.txt file for an entire make file » Create an option to generate a single PATCHES.txt file for an entire make file

Actually, thinking through how this will work with recursive make files, this will be much better as an option to make, rather than a separate command, since the make file must be built to determine all patches.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
StatusFileSize
new drush-make-patches-option-1465810-02.patch2.22 KB

This is a start at an option for this. I got stuck trying to collect *all* patches from various backend calls. This patch uses a context (trying to model after my understanding of how logs are gathered across backend calls), but obviously needs work as the patches are coming up empty.

dww’s picture

dww
we/he/they
commented

Lots of discussion of this already at #910732: RFC: PATCHES.txt format -- tempted to call this duplicate.

Also, we're already doing something similar at #1433784: Fix how drupalorg_drush handles release history XML and propagates data to the packaging script by writing out a single .json file that includes data about everything drush make does, including which releases it downloaded, what libraries, and what patches were applied. This would be used by the d.o packaging script to more accurately be able to record and display the contents of packaged distros, but if that basic approach seemed legit and useful, we could certainly move that into drush make itself.

greg.1.anderson’s picture

greg.1.anderson commented
Version: » 8.x-6.x-dev
Status: Needs work » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.