Changes to your 5.0 .info files
Over the last couple of days, the core committers have given us some excellent UI changes which require some minor support in your module .info files: [Note: Actually, none of this is required]. 1) We now have dependencies. List dependencies in your module.info like so: dependencies = views [to make your module require views before it can be enabled]. You can list multiple modules, separated by a comma. 2) We now have package grouping on the module administration page. If your module is part of a multi-module package (ecommerce and CCK are super obvious choices) then adding: package = ecommerce is a good thing. Modules that are designed for these packages can also use these keywords. For now, if your module is basically a standalone module, it is best to leave this blank and let your module appear 'uncategorized', as a lone module in a package will not be terribly useful.
On 5-Oct-06, at 12:10 PM, Earl Miles wrote:
2) We now have package grouping on the module administration page.
If your module is part of a multi-module package (ecommerce and CCK are super obvious choices) then adding:
package = ecommerce
Is the intention here to tie these to the categories in use on the module download page? Anyone written up (or given thought to) guidelines here? Any relationship between packages and dependencies? -- James Walker :: http://walkah.net/ :: xmpp:walkah@walkah.net
James Walker wrote:
On 5-Oct-06, at 12:10 PM, Earl Miles wrote:
2) We now have package grouping on the module administration page.
If your module is part of a multi-module package (ecommerce and CCK are super obvious choices) then adding:
package = ecommerce
Is the intention here to tie these to the categories in use on the module download page? Anyone written up (or given thought to) guidelines here? Any relationship between packages and dependencies?
No; I've always believed (personally) that the categories used for finding and downloading modules is completely unrelated to the categories used when administering modules on your site. For one, you will have a LOT fewer modules on your site than you download; and for two, the primary use of the package is so that modules that are packaged together can be listed together, or so that modules that are meant specifically for use with other modules can be listed with that module. There is, in fact, no real relationship between packages and dependencies beyond the fact that they both exist on the modules page, in the .info file, went in about the same time, and often modules in a package will have cross dependencies on each other.
Is the intention here to tie these to the categories in use on the module download page? Anyone written up (or given thought to) guidelines here? Any relationship between packages and dependencies?
I guess the head honcho (Merlin for views, Gordon for ecommerce etc) will put his module in some package and the herd will simply follow. I do not see any close relation between the two. While inside one package there could be many dependencies, votingapi is hardly a package and yet many modules rely on it. NK
participants (3)
-
Earl Miles -
James Walker -
karoly＠negyesi.net