In "Development" package?
neurovation.kiwi - August 9, 2009 - 13:04
| Project: | Drupal For Firebug |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi Folks!
kudos for this great module - but should this not be in the "Development" package (instead of the "Drupal for Firebug") according to the .info file?
maybe you also get the developers from "Devel" to add you in their standard "Developer modules"!
cu
kiwi
#1
BTW, The package information in .info files is *not* a taxonomy system. See http://drupal.org/node/231036 for the proper use of package information. If we want to make the admin/build/modules page classified by taxonomy, we should do it properly and refactor the entire page. I also made a small contrib module (Module taxonomy) so people could alter the package information for the modules on their own site.
This module should not include a package line in the .info file.
#2
don't want to be a smart ass, but i looked once more at the link you provided:
package (Optional)
[...]
The exception to this rule is the "Development" package, which should be used for any modules which are code development tool modules (Devel, Coder, Module Builder...).
As this module is clearly used for development, it should be listed in the package "Development" than the "DrupalForFirebug"
#3
Well, then my apologies. I swear that wasn't in there before, but it was and I just missed it. I have no problem with this then. I'm just sick of people requesting to misuse the package line, and I've had requests for several of my modules. Adding one single module to the "Administration" package does not help solve the underlying problem. Continue on. :)