It would be very useful if there was a patch management system built into Drush's package manager. This would let administrators/developers use stable versions of a given module and then apply patches to that module automatically. By tracking patches separately from the 'upstream' modules, there can be a better separation of site-specific/local changes and provided changes.

Additionally, it then becomes easy to create a drush command which can generate a patch based on the upstream module source and your current working directory. In addition to being a handy timesaver, this could be very useful for people not as familiar with 'diff', but who can contribute useful code changes.

An example of this system is:
http://web.media.mit.edu/~stevep/drupal/module_manager.py

which is a python script that does just this. While it functions as described already, it may make sense for this functionality to be built into Drush as well.

CommentFileSizeAuthor
#1 kitten_o_matic.drush_.inc_.txt4.17 KBgreg.1.anderson

Comments

greg.1.anderson’s picture

Status: Active » Needs review
StatusFileSize
new4.17 KB

Funny you should happen to mention that (a year ago...).

A while back (much less than a year ago) I put together this little ditty called 'kitten-o-matic'; while this is not exactly a "patch manager" per se, it will automatically apply any patch files it can find any time a module is downloaded or updated. It is also useful for insuring that fckeditor gets copied into the fckeditor module, for example.

As its name implied, this command is somewhat dubious in terms of its workflow (checking your modified files into a vcs is probably a better way to go), and I'm undecided as to whether this will even be included in drush extras. However, it is here and available for review by any interested party. Just move to your .drush folder and rename to *.drush.inc.

Patches and improvements welcome.

greg.1.anderson’s picture

Status: Needs review » Needs work

I'm not going to commit kitten_o_matic to drush_extras, but additional work along the lines of the code referenced in #0 would be welcome here.

colan’s picture

Status: Needs work » Closed (duplicate)

It's probably best to put all efforts toward #1078108: Drush issue queue commands.

greg.1.anderson’s picture

Title: Patch manager » Kitten-o-matic

Renaming closed issue for posterity.