2

Currently in my booking_timeslots.info I've the following dependencies:

dependencies[] = date
dependencies[] = date_views
dependencies[] = hierarchical_select
dependencies[] = hs_taxonomy
dependencies[] = hs_taxonomy_views

which fails with the following errors:

No release history was found for the requested project (hs_taxonomy_views).

No release history was found for the requested project (hs_taxonomy).

No release history was found for the requested project (date_views).

when I'm trying to either enable the module, or installing it with quick-drupal command like:

drush qd --yes --core=drupal-7 testsite booking_timeslots

How do I specify to which main project they belong to, so the installation process won't fail?


Personally I know to which modules they belong, but I would like to automate this process, ideally by adding appropriate syntax into .info file so other services can understand its dependencies (such as drush). It seems running module in Simplytest sandbox can recognise these dependencies fine.

I can't find anything relevant in .info syntax docs apart of specifying (major.minor).

3

You can declare the project name of the dependency using the following syntax:

dependencies[] = project:module

However, this this is a new feature that was added in Drupal 7.40, and as far as I can tell, Drush doesn't seem to understand it yet.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.