[development] RFC: Module checksum module

Larry Garfield larry at garfieldtech.com
Wed Feb 11 17:49:37 UTC 2009

For this to be really useful, it would need to integrate into update.module.  Doesn't Acquia Drupal include something like this already?  Could that be generalized?

(Many of us check modules out from CVS directly, but many of us don't.  I don't, generally.)

--Larry Garfield

On Wed, 11 Feb 2009 12:46:49 +0100, Olivier Jacquet <ojacquet at jax.be> wrote:
> Hi,
> When developing with Drupal you often use contrib modules. When using
> contrib modules it happens that you find a bug or need it to behave
> differently than what was intended. So you modify the module.
> Now you have to have a method for knowing that this module is no longer
> the stock contrib module. I've seen different shops hande this in
> different ways but never really in a robust way.
> That's why I want to suggest the "module checksum" module. When you
> activate a module, the directory it is in is checksummed and the result
> stored. The module then allows you to rerun the checksum against all
> modules and shows for which modules the new checksum no longer matches.
> These are the modules that have been modified. With this list you can
> make sure you have the necessary patches before you upgrade said modules.
> I've briefly looked around and have not found anything like this. Is
> there? Any other suggestions or remarks? If not, I think I'll go ahead
> and make it.
> Best regards,
> Olivier

More information about the development mailing list