The clone module would then depend on them. That would allow other modules (like Cash Flow, which is my case) add a dependency on node_clone as well as clone, and Drush would then be able to download Node Clone properly. As it is, it'll either say that it can't enable node_clone or it will keep complaining that clone doesn't exist.

This isn't a functional change for the module. Other than the basic stuff in node_clone.info, the placeholder files could be empty.

I'm willing to roll the patch if it would be reviewed.

CommentFileSizeAuthor
#5 1919168-5.patch459 bytespwolanin

Comments

pwolanin’s picture

pwolanin commented
Issue summary: View changes

How does this work for any other module where the project name and the module name are not identical?

wizonesolutions’s picture

wizonesolutions
he/him
Primary language English
Location Norway
commented

I don't know. Is this something that has been raised, or that we should raise, upstream?

lolandese’s picture

lolandese commented
Related issues: +#1325940: Namespace is "node_clone", but is named "clone" module
pwolanin’s picture

pwolanin commented

This idea is probably the less annoying solution.

Can we make it a hidden module?

pwolanin’s picture

pwolanin commented
Status: Active » Needs review
StatusFileSize
new 1919168-5.patch459 bytes

Not sure I love this, but please test and see how it works for you.

paulvandenburg’s picture

paulvandenburg commented
Status: Needs review » Reviewed & tested by the community

#5 has been solving this problem for us for quite a while now, since #2989434: Use node_clone module instead of clone to be exact.
I'm for including this in the next release.