Hi, Some community modules are incompatible with each other, or with core modules. It may not be desirable but it is sometimes unavoidable and is a fact today. Discovering such incompatibilities is a painful process, and there is no structured mechanism to communicate about them once they have been (re)discovered.
This has been discussed in the past [1], but was not followed by concrete steps, AFAIK. As a first step, would the community agree with the addition of a field named "incompatible" in __openerp__.py, providing a simple list of module names that are known to be incompatible? This would be beneficial to the community, even without support in the core or apps.openerp.com, by letting module maintainers declare known incompatibilities. Populating this field can follow the normal merge proposal and review process. If it gains traction, tooling may support it in a second step. Note that I consciously avoid the topic of version dependencies as this would open a bigger can of worms. The only purpose of the present proposal is to provide a human and machine readable way to document partitions in the addons landscape. Cheers, -sbi [1] https://lists.launchpad.net/openerp-expert-framework/msg00840.html Stéphane Bidoul | @SBidoul <https://twitter.com/SBidoul> Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp