Skip to content

Install via pip - how to proceed when a module already exists? #88

@JordiBForgeFlow

Description

@JordiBForgeFlow

Currently if you have an existing installation that contains an OCA module installed using pip, that perhaps was installed referring to a PR, and then this PR is merged into OCA, you may get this situation when you do pip install -r requirements.txt:

What to do? (s)witch, (i)gnore, (w)ipe, (b)ackup

The problem is that ansible runs all the steps automatically, and this one is treated as an error.

Perhaps in the ansible role we should always wipe all the OCA modules every time, or force update of them all?

One thing I do not like with the ansible approach is that in general, as the ansible role evolves, the old packages, python modules, etc.. are not going to be removed. This is something that Docker does better, as it creates from scratch every time, ensuring that there's no artifact sitting in the server that is not included in the configuration files.

cc @sbidoul perhaps you know how to force the pip install to always wipe the old pip module?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions