Some people consider it bad practice to have different machine names for a module and its project. I, for one, have an expectation that drush dl ftools can be followed by drush en -y ftools. Would you consider renaming the features_tools module to ftools (a much nicer name anyway, IMHO) now while it's comparatively young? I would be happy to write a patch to get things started.

Comments

osopolar’s picture

osopolar
Primary language German
Location 🇩🇪 GER 🌐
commented

+1 to have the same name for project and module. If you call it features_tools or ftools I don't care that much, but I find features_tools is more descriptive.

perelman.yuval’s picture

perelman.yuval commented
Assigned: Unassigned » perelman.yuval

Hi TravisCarden and osopolar, thanks for the issue.
I will change the module name to ftools in the near feature.

core44’s picture

core44 commented

I have a problem here when deploying and enabling development features that contain ftools as a dependency. When enabling the feature, Drush tries to auto download features_tools and finds no release history.
No release history was found for the requested project (features_tools). [warning]
I currently have to download it separately as ftools on each install before I can enable the dev feature.

Thanks for the very useful module.

slcp’s picture

slcp commented

@perelman.yuva - Is there any movement on this?

perelman.yuval’s picture

perelman.yuval commented

Hi all, i changed the module name to ftools.
And add a new relase 7.x-1.6
It will be added in the next hours.

perelman.yuval’s picture

perelman.yuval commented
Status: Active » Closed (fixed)
jzornig’s picture

jzornig commented

Broke my feature that had this as a dependency. But now I worked out that you changed the name I can rebuild against the 1.6 version and include a dependency on ftools.