By ojkelly on

Hey everyone

with the new module.info files there is a properties/attribute for package, undoubtedly if you been making modules for drupal 5 then you would have come across it at some stage. info on it here http://drupal.org/node/64279#info

it also says

If you assign a package string for your module, on the admin/build/modules page it will be listed with other modules with the same category. If you do not assign one, it will simply be listed as 'Uncategorized'. Not assigning a package for your module is perfectly ok; in general packages are best used for modules that are distributed together or are meant to be used together.

Now if in a couple of months like with 4.7.x there will be a lot of modules. And currently there is no conventions for the package property.

This package property has the potential to make the module page very clean and easy to read, but at the same time it could make it very messy and hard to read.

I propose to avoid the latter that we set some conventions for packages.

If you look at the current module page you'll see there is already a lot of categories. My idea is that we use those categories as the package.

eg
3rd party - Flickr
3rd party - Amazon

etc.

⋅ Categories: Drupal 5.x

Comments

ufku’s picture

ufku commented

+1 on using module categories. Modules that go into more than one category may select the best fitting one. Actually i didnt define a package for my module yet. I'm waiting for a trend formation on this. I think the rating of this topic will increase with the increase of modules being ported to 5.

--
Geneticists from METU