[development] 4.8/5.0: Modules, the install system, and directories

[Adrian Rossouw]

On 22 Feb 2006, at 10:00 PM, Morbus Iff wrote:
> Do I want the ability to move help into our meta info file? Yes. Am  
> I thinking about that right now? Yes. Ignoring the technical  
> limitations of moving help outside of .modules in general, do I  
> believe that .ini files can satisfy the help desire? No. Do I see  
> the move from .sql files to .install files being indicative of a  
> future possibility with the non-logical .ini files? Yes. Do I want  
> to make the same mistake? No.
all I'm really opposed to is requiring a function definition for the  
meta information inside the file. Because a lot of the places I see  
the meta information being used are not modules,
that might need to be copied around, taking the name from the  
directory they are in (the themes/style example).

We could also just include the meta files from within a function and  
use get_defined_vars() to retrieve the variables.

oh .. and themes are a great place for knowing that files have  
changed, since most people modify them directly in the directory,
hence disabling the theme and using a safe default after upgrade  
might be a good way of stopping theme breakages, for instance)

If a module distributes template files that are overridden, it might  
also be useful to know which template files in the theme you are using
might be out of date.

--
Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com