There is also another module for developers http://drupal.org/project/patchdoq

PS : I like your module thanks for sharing

Comments

sinasalek’s picture

sinasalek commented

Patchdoq module seems abandoned, do you have any plan for providing API.
I've had several suggestions for patchdoq module:
http://drupal.org/project/issues/patchdoq?categories=All

aidanlis’s picture

aidanlis commented
Status: Active » Closed (fixed)

Yes, I'll provide an API and drush integration.

ClearXS’s picture

ClearXS commented
Status: Closed (fixed) » Active

It is active, there was a dev update a few months ago.

http://drupal.org/project/patchdoq

What are the differences?

Could these modules be merged?

Same questions I've placed there: http://drupal.org/node/909494

aidanlis’s picture

aidanlis commented

Ah how interesting. patchdoq's approach covers an aspect that I'd been thinking about for a while, how to handle patches that come with modules, e.g. smtp module, simpletest, etc.

I think it would be great to merge the functionality of patchdoq into patch_manager, and I'd certainly appreciate having another maintainer to work with me on this.

Note: I think patchdoq should be merged into patch_manager rather than the other way around because:
a) patch_manager is a more generic name.
b) patch_manager's architecture is newer (it uses nodes, cck and views) which makes it much more extensible
c) patch_manager has a better growth curve, as of next week more people will be using patch_manager than patchdoq.

doq, let me know what you think, I'm keen.

aidanlis’s picture

aidanlis commented
Title: patchdoq module » Merge features from the patchdoq module
klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

@ClearXSClearXS #3: There was a build bot/server hick-up in 2010-Jul-11 that caused ALL modules/themes to rebuild their dev versions. This doesn't mean that the module is active or that its code was updated at that date. The maintainer made his last code commit 1 year ago and almost all issues in the module's queue date one year or so back too (with no reply from the maintainer). Tracking the user shows that his last activity in drupal.org was a post made more than two months ago.

...Thus, I think it is quite safe to assume that the maintainer has lost interest for that module or has no free time. Seems like an abandoned module to me.

sinasalek’s picture

sinasalek commented

@ClearXSClearXS you might as well check cvs log messages for that purpose that's more accurate

aidanlis’s picture

aidanlis commented
Status: Active » Fixed

I've added support for hook_patch, so that's patchdoq integration done.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

...what about your comments/plans in #2 and #4 Aidan? I mean what do we have now? API? Drush integration? Handling of patches that come with modules?

aidanlis’s picture

aidanlis commented
Title: Merge features from the patchdoq module » Import and apply patches that implement hook_patch
Status: Fixed » Postponed

I'll rename this bug to keep track of this functionality specifically. hook_patch is implemented, but the module is not doing anything with it yet.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

thanx ;)

paulgemini’s picture

paulgemini commented

subbing

sinasalek’s picture

sinasalek commented

Thanks for implementing , hook works but as you mentioned doesn't do anything other than list the patch which could be achieve anyway using the scan feature
I think the most important thing we need is for patch manager to handle applying third-party patches and also reports their status as well. This way we can keep patches completely in code which i think is more appropriate considering the fact that in Drupal 8 configurations are going to be in file.
Module can automatically add patches introduced via hook_path to database (patch path as key) and remove the one that no longer exist
A new token item in patch info is also required i think to check whether the patch is applied or not

aidanlis’s picture

aidanlis commented

I don't have time to work on this ... but if someone wants to help out let me know.

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented
Issue summary: View changes

Make a patch an entity api entity or a ctools exportable and they can come from hooks.