Contributors mailing list archives

Browse archives


Re: 14.0 branches

Camptocamp SA, Simone Orsi
- 09/10/2020 15:45:39
Hi Daniel,

IMO even if you see the list of repositories you still don't know which module is used and by whom.

On the contrary, with the dependency coming from python packages, you can list the tree of the dependencies pretty easily.


On Fri, Oct 9, 2020 at 3:11 PM Daniel Reis <> wrote:
On 09/10/2020 11:32, Stéphane Bidoul wrote:


> @Simone, I think it's too early to say the other way is deprecated. 

> Let's give it some time.


Thank you for this work,

The oca-dependencies.txt solution was a bit clumsy, and probably it is a 
good thing that is is being sunset.

But I miss a way to get the equivalent information it gives me today.
If I deploy from Git sources (I think most people do), the 
oca-dependencies.txt gives me good clues about what other OCA repos I 
should be also including in my project.

I see some frustration coming, from not knowing what other repos we need 
to deploy to make the used modules work.
Forcing people to still maintain oca-dependencies.txt is not a good 
solution. Since it is not used in tests it is not assured to be 
reliable, and it will still have the problem of being a repo-wide 
dependency, and possibly too much for the particular modules I'm 
interested in..

I would rather prefer to have a way to have the dependency repo 
information, based on particular modules.
It would be perfect if I could run a command that would five me this 
If not possible, we should required the module README to state these 
dependencies, in the Install section.


Post to:

Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, Freelance in love with open source.