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
bee
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 'conflic
Le 17 août 2013 14:06, "Stefan Rijnhart" a écrit :
>
> 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?
On 2013-08-17 14:06, Stefan Rijnhart wrote:
> Yes, totally. Slight preference for calling it 'conflicts',
> analogous to the existing 'depends' directive.
Which is the well-known Debian terminology. Nice! :~)
(Btw. there are also: Recommends, Suggests, Enhances,
Replaces, ... - not yet needed her
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.
Do you have some examples of incompatible modules where it's unavoidable?
My first though would be to understand why a module ma
On 08/17/2013 04:03 PM, Fabien Pinckaers wrote:
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.
Do you have some examples of incompatible modules where it's unavoidable?
Hi Fabie
Hi Fabien,
On Sat, Aug 17, 2013 at 4:03 PM, Fabien Pinckaers wrote:
> 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.
>
>
> Do you have some examples of incompatible modules wh
I agree with Fabien. Having this conflicts field will also legitimate
incompatibilities and they will remain forever.
Not having this field will force people to collaborate and solve the conflict
when discovered.
My 2 cents.
--
Maxime Chambreuil
+1 (514) 276-5468 #126
- Mail origin
On Sat, Aug 17, 2013 at 5:32 PM, Maxime Chambreuil <
maxime.chambre...@savoirfairelinux.com> wrote:
> I agree with Fabien. Having this conflicts field will also legitimate
> incompatibilities and they will remain forever.
>
> Not having this field will force people to collaborate and solve the
> c
On 08/17/2013 05:32 PM, Maxime Chambreuil wrote:
Not having this field will force people to collaborate and solve the
conflict when discovered.
Not particularly. I remember the first time someone told me that Banking
Addons were incompatible with account_bank_statement_extension. I did
not
On 08/17/2013 06:45 PM, Stefan Rijnhart wrote:
As the defacto maintainer of the Banking Addons, I do not feel forced
to collaborate and integrate with alternative solutions. I might think
it is a good thing if I see added value for my company or my customers
in any way, but I am not forced.
B
+1, I still feel this is needed.
Fabien : I've seen at least one re-implementation of MRP in the wild,
which are obviously not compatible with the official mrp addon. Just
having a comment in the description of the module is not enough : we
need something stronger which prevents accidental install
+1
Yes conflicts between module could be registered as a bug... But meanwhile
it's already too late for production environnent and complicate and time
consuming on dev/delivery context to investigate why it's bugging. It costs
money and generate delay on project development. Anyway this kind of
ex
+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 pr
Hi there,
On 08/17/2013 12:41 PM, Bidoul, Stéphane wrote:
> 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 i
15 matches
Mail list logo
