[development] CCK field modules maintainers - D6 upgrade path

[Jakob Petsovits]

On Saturday 06 September 2008, Yves Chedemois wrote:
> To all CCK field modules maintainers :
> please read http://drupal.org/node/304813

It would make a lot of sense to also have this in the handbook, at 
http://drupal.org/node/191796

Of course, with inter-dependent module stacks getting popular, the nifty 
solution would be a solution in Drupal core, like, say,

mymodule.install:
...
/**
 * Implementation of hook_update_dependencies().
 * Not necessary to implement if this module's update functions do not
 * depend on other module's updates.
 */
function mymodule_update_dependencies() {
  return array(
    6000 => array(
      'content' => 6000, // needs at least CCK 6.x
      'filefield' => 6301, // and filefield-6.x-3.1 (made up the update no.)
    ),
  );
}
...

Those upgrade dependencies are (still?) so much of an edge case that a lot of 
module developers are apt to ignore them, while with a centralized framework 
it would be easy to implement, with updates being less error prone. Plus 
instead of aborting the whole process like in the above CCK note, those 
updates could run correctly in one go.

Seems easy enough, but I don't exactly feel strong enough about that idea to 
implement it :P