Basic on dependency management

[egekorkan]

There are two things missing about dependencies in my opinion.

1. How to tell a user how to install them: This depends on the language but python has this requirements.txt and setup.py convention. Poetry is a new way to manage them, I don't have much experience but for me that is finally the direction for python dependency management. (https://python-poetry.org/). In JS, package.json existed for a long time and manages this in an OK way. In any case, so many sw packages on GitHub repositories list the dependencies in the Readme.md in a textual way but it is always better to provide a simple way for the user. The above-mentioned methods also assure version management, giving you more hopes that the user will not install a dependency that is not the right version you need.

2. How to manage the dependencies as the developer: So using another package that satisfies your need is not necessarily a bad thing to do. If you are using one, you have to manage it and its version. Thus, you should definitely note the version you are using (ideally in a dependency management convention). In addition, we might be able to give tips on whether to add them or not. Reminding developers that a dependency also has its own dependencies and you can end up in a software package where you have more than 100 resolved dependencies. So encouraging people to no use dependencies for simple things is good in my opinion.