[drupal-devel] RFC: drupalversions.module

neil at civicspacelabs.org neil at civicspacelabs.org
Thu Jul 28 17:59:12 UTC 2005

On Thu, Jul 28, 2005 at 10:26:52AM -0400, eric Farris wrote:
> I am in no position to start contributing code to this at present, but I
> plan on doing so if there is such a need. I still don't know what the
> hook would look like or what the schema would be.
> So...  what do you think, sirs?

I think this sort of thing is much needed, but I'm not sure that it fits
well with the previous work at http://drupal.org/node/22472.

For example, I am currently working on update.php with the plan of
making it able to manage the database tables for all modules, not just
Drupal core. The DB schemas need to be versioned. The numbering scheme
will be similar to that used in database/updates.inc today.

A CVS id would not work in this case because those are simply too
unpredictable for use elsewhere. Even for tracking compatibility of the
module itself (works with 4.6.x, etc) I imagine matching the
auto-genrated ids to be infuriating for many developers. There is simply
a large learning curve to to figure out what system the CVS numbers use
and be able to precict which number will be next.

I suppsoe there could be something that scrapes this information out of
the CVS repository by looking at the tags. That would make us dependant
upon CVS and feels like an overly-complex system.


More information about the drupal-devel mailing list