+1 - I like that idea.
However, I don't see it gaining much traction since the 'proper' way to
do it is to roll a release for each version of core. Also, I think the
strategy I outlined below is quite messy, and probably shouldn't be used
unless there were extenuating circumstance which required you to include
several versions of the same module compatible with different versions
of core within the same download.
Brian
Aaron Winborn wrote:
If folks start doing a lot of that, might be nice to add support for
an 'ignore-if-not-supported' property or something to the .info file
so it doesn't show up w/ a warning in the other version.
Brian Vuyk wrote:
That is, you could probably release a folder structure / package
along the lines of:
mymodule/
includes/shared.inc
mymodule_d6.module
mymodule_d6.info
mymodule_d7.module
mymodule_d7.info
Where 'includes/shared.inc' would include logic shared between the
two different modules. Both modules would show up on the 'Modules'
page, but only the one corresponding to the correct version of Drupal
could be enabled.
