.info file requirement for Drupal 5 [#103457]

Please find the info file required by Drupal 5 attached. I haven't tested yet with version 5 but to get anywhere with it we need this new file. I've given package a value of Email because the ``package'' is really a type declarer to group common things in the new menuing system. I really would like to promote your return-path package as a Drupal Core Optional module or better to create a patch to Drupal Core itself as your methods being the only way the return path is set but that is probably a harder sell.

Earnie
http://for-my-kids.com
http://give-me-an-offer.com

Comment	File	Size	Author
	returnpath.info	265 bytes	Anonymous (not verified)

Comments

Comment #1

heine commented 15 December 2006 at 15:22

Status:

Needs review

» Needs work

Just some additional information: package should probably be empty per Writing .info files (Drupal 5.x).

Comment #2

Anonymous (not verified) commented 15 December 2006 at 18:03

I disagree with that point when a package grouping is a little obvious. The menu group 'Other' will be excessively large if we don't try to use package to sensibly group the menu. It is intuitive that the returnpath module affects Email so the grouping Email should be used to help the user find the configurations related to controlling Email.

Comment #3

heine commented 15 December 2006 at 19:02

It is package, not category. For background; see for example the devel list thread @ http://lists.drupal.org/pipermail/development/2006-November/021069.html

Comment #4

Anonymous (not verified) commented 15 December 2006 at 20:14

I agree that package isn't the correct term and that itself has bothered me. I can see category as being more correct a term for what I would like to see the current package to be used for but even package_type may be better. I do agree that module maintainers/contributers should not be the decision maker of the package/category because different people think different ways and there would be no consistency. I do not agree that we should leave all of the unspecified packages in the "Other" package/category. I do agree that for version 5 package should be unspecified for this module because of the decisions made prior to my input. I also think that the info file needs a conflicts variable to identify contributed modules that conflict with one another and a suggested variable to indicate other modules that make a module more robust but are not required however that is a different issue.

I've just registered for a developer list account. Drupal development is quickly becoming very important to me.