[development] Version2 Module

[Doug Green]

It reads the system table for a list of enabled modules.  It then filters
out core modules (based on name and the Drupal constant VERSION).  

It makes a pretty good attempt at determining the project name (works for
every module I've tested with), and gets the latest CVS Id for that project
module.  When there are two modules in one directory, views being a good
example, it displays both modules and tells the administrator that both
modules can be upgraded.  This is a great point!  I should probably change
it so that it groups modules into projects and only displays project upgrade
notices (instead of the current module upgrade notices).

It does not handle anything except .module files (.inc, .info, or .theme).
This is a shortcoming that should/will be fixed by the project.module and
the .info packaging information.  I'll work in this direction.  But I think
we all recognize that this information is not available in 4.7.

Doug Green
www.douggreenconsulting.com
www.civicactions.com

-----Original Message-----
From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
On Behalf Of Earl Miles
Sent: Wednesday, January 03, 2007 9:21 AM
To: development at drupal.org
Subject: Re: [development] Version2 Module

Doug Green wrote:
> I don't think it's as bad as Dries says.  It wasn't a waste of time
because
> this module will help some people with the 4.7 -> 5.0 upgrade (me being
one
> of them).  For it to be useful to the Drupal masses, though, it needs to
> (and will) use the new project system.

How does it handle module .inc files? (Example: views_query.inc)

How does it handle multiple modules in the same directory? (Example: 
views_ui.module) -- these are two of the reasons I've preferred to avoid CVS
at 
all for this kind of thing, and why I think doing this will end up getting
your 
users into some trouble.

I've been trying to set aside some time to help Derek out by writing an
xmlrpc 
interface to get project info, as discussed in the thread Derek has
mentioned a 
couple of times, but I haven't been able to fit it into my schedule. I think

such a project is very simple. And once you can query it...yes, it's going
to 
be difficult with 4.7 because you won't have the project info, but in 5
you'll 
have it.

The 4.7 --> 5 problem might be well served by creating a module that guesses
at 
the information and does some queries, and lets the users fill in
information 
it guesses at incorrectly.