I'm about this:

 function _hosting_package_types() {
  return array(
    'profile' => t('Installation Profiles'), 
    'module' => t('Modules'), 
    'theme' => t('Themes')
  );
}

What about 'Libraries', 'Translations' [, 'Tests']?. IMO we need a hook for pluggable package types. Modules could provide additional instructions for platform build and install processes.

Maybe a stupid question: where's 7.x-2.x issue queue? This code is still 6.x.

Comments

steven jones’s picture

steven jones commented
Status: Active » Postponed (maintainer needs more info)

I'm not sure we'll be able to track those other packages, because they don't have .info files, so drush will be unable to work out which version of the library/translation is in the platform.

Could you provide more details about what you'd envisage this doing and possibly some details about how it could work?

tema’s picture

tema commented

Hmm.. I'd not thought about .info files. So it means that libraries are unmanaged now?

My thoughts are about some custom behavior for that types. It seems that I should digging more.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Until Drupal starts tracking these, I don't think we'll be able to. Feel free to re-open when that day comes, or someone has a good idea of how to implement this.