Contributors mailing list archives
Re: 14.0 branchesby
Acsone SA/NV, Stéphane Bidoul
I agree that oca_dependencies.txt remains valuable as documentation and was thinking about that too.
A good source to know in which repo each addon is located is odoo-community.org/apps.
Another one is pypi.org where each addon has a Homepage link to the repo.
It's probably quite easy to write a script that extracts that information from a list of addon names, and eventually generate oca_dependencies.txt.
@Denis, I agree with you of course, but the point here is certainly not to force everyone to use that method in their own projects.
On Fri, Oct 9, 2020 at 3:11 PM Daniel Reis <email@example.com> 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 information. If not possible, we should required the module README to state these dependencies, in the Install section. Thanks Daniel