the .info files should have a line to list modules with which the module conflicts with. that way if you have two modules that perform the same function and step on one another, they could be marked that way. The module admin page could tell you that you are enabling conflicting modules, and of course tell you that they conflict before you enable them.

Comments

Version:5.0-beta1» x.y.z

sorry, 5.0 is closed for feature requests

Version:x.y.z» 6.x-dev

moving from x.y.z to 6.x-dev version queue

+1 for this. I would use if available in my video module.

Fabio Varesano

What ever came of this? I'm working on a pricing level module that directly conflicts with Role Discounts. I'd love to be able to say that in my .info file.

I would like this functionality to, mainly to prevent namespace conflicts.

+1 For example, the 5.x cck date field conflicts with the 5.x event module, with this feature, one could be prevented from installing the cck date module until the event module was disabled.

Version:6.x-dev» 7.x-dev

Marked #170424: .info file should support negative dependencies as a duplicate of this issue.

While we're at the "dependencies feature" stage, it would also be nice to have a way to indicate when a module does not actually "need" an other module, but has added features when it is present. This would remove a burden from contrib module devs who need to add specific code for this to their module, while a core mechanism could allow refactoring all this contrib-specific code to just one standard way of having such optional dependencies expressed.

Subscribing.

Subscribing.

Added a patch to the issue mentioned in #12, #328932-66: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files, which could be built upon to solve this issue. If that issue develops in the direction of my patches then this issue perhaps should be postponed until that issue has been solved.

Version:7.x-dev» 8.x-dev

subscribing

I think modules like admin_menu vs toolbar would benefit from this implementation

Title:Modules in conflict - conflicts[], breaks[], brokenby[] field in modules .info filemodule .info files should have a field for conflicts
Component:system.module» base system
Issue tags:-conflict, -.info file, -.info, -conflicts

we need these:
* conflicts[] - module(s) that can NOT be enabled when enabling this module (ERROR)
* breaks[] - module(s) that will NOT work after enabling this module (WARNING)
* brokenby[] - module(s) that will make this module NOT work after being enabled (WARNING)

see:
#328932-153: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
#328932-139: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
#328932: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files

Title:module .info files should have a field for conflictsModules in conflict - conflicts[] and breaks[] field in modules .info file
Component:base system» system.module
Issue tags:+conflict, +.info file, +.info, +conflicts

Title:Modules in conflict - conflicts[] and breaks[] field in modules .info fileModules in conflict - conflicts[], breaks[], brokenby[] field in modules .info file

actually, we should use brokenby[] instead of breakedby[].

english lessons reminded me of broke/broken and simple past and past participle, so i read a bit to make sure:
http://en.wiktionary.org/wiki/break
http://en.wiktionary.org/wiki/breaks
http://en.wiktionary.org/wiki/broke
http://en.wiktionary.org/wiki/broken
http://en.wiktionary.org/wiki/enhance
http://en.wiktionary.org/wiki/replace

Title:module .info files should have a field for conflictsModules in conflict - conflicts[], breaks[], brokenby[] field in modules .info file
Component:base system» system.module
Issue tags:+conflict, +.info file, +.info, +conflicts

This has been open for half a decade and seems very useful. Can we get this into D8?

maybe d9 it will be :(