WrapEarnPass left a comment (geany/geany-plugins#1570) It's poor development practice to track another project's master unless you are intending to make changes in that project's master too.
As a geany-plugins developer, I want stable depends-on so I know if problems I see are most likely my problems, or if I have to start looking through other projects. geany-plugins is related to geany, but they are different projects. geany-plugins expresses that relationship though the build requirement, just like for gtk, and scintilla. Advertising that geany-plugins@master will build against geany-2.1 in the build system should mean that I can pull down the changes in geany-plugins@master to use against my system installed geany-2.1 without having to expect to recompile geany too. That expectation does not hold, so geany >= 2.1 is invalid, and the actual expectation, at least for glspi_app.c is geany == 2.2. either the plugin that has that dependency or the geany-plugins project should express that requirement. Taking the vice-versa, if I was to be a geany developer, I would like to ensure any changes I made don't break dependent projects, this should allow me to build geany@master, and load a dependent against my changes. In this case, that works perfectly. geany@master will load a system geany-plugins-2.1. [email protected] validly expresses a dependency of geany >= 2.1 <img width="472" height="251" alt="Image" src="https://github.com/user-attachments/assets/803408fa-11c6-4dda-91f2-62abf76bbe20"; /> This means that all these criticals probably have to do with the changes in geany, and not something in plugins. <img width="991" height="464" alt="Image" src="https://github.com/user-attachments/assets/9e4fdaf8-3a4c-4f3b-8827-849e06be26c2"; /> -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1570#issuecomment-4825956491 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/issues/1570/[email protected]>
