+1 on having "conflicts" field. Even if some incompatibility is not unavoidable and can be considered a bug, the module should be marked as incompatible until the conflict is resolved. Also If you know beforehand that some module is incompatible, you can plan a budget to resolve the conflict and propose a patch for it. Without this field you sometimes hit incompatibility problems when it's too late.
Cheers Tymoteusz 2013/8/17 Stefan Rijnhart <[email protected]>: > On 08/17/2013 12:41 PM, Bidoul, Stéphane wrote: >> >> >> 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? >> > > Yes, totally. Slight preference for calling it 'conflicts', analogous to the > existing 'depends' directive. > > Cheers, > Stefan. > > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp -- Pozdrawiam serdecznie / Best regards Tymoteusz Motylewski Head of development +48 502 472 202 [email protected] http://www.macopedia.pl/ Ul. Roosevelta 5/8 60-829 Poznań Tel. +48 61 622 96 95 Fax +48 61 623 24 48/ Macopedia Spółka z ograniczoną odpowiedzialnością, z siedzibą ul. Roosevelta 5/8; 60-829 Poznań, wpisana do Krajowego Rejestru Sądowego, prowadzonego przez Sąd Rejonowy, VIII Wydział Gospodarczy, KRS 0000416744, o opłaconym kapitale zakładowym w wysokości 5.000,00 zł, o numerze NIP: 781-187-78-41, numerze Regon 302076699 _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
