> I remember having this problem when switching between meson build and > autotools build - each of them installs geany.so to a different location - > autotools to /usr/local/lib and meson to /usr/local/lib/aarch64-linux-gnu and > I think the latter one takes precedence. If there were a way to unify this > behavior, it would be great to avoid similar problems.
It would be good to fix it. IMO (at least on my Mint machine) meson used the right place, and autotools used the wrong one. Geany was the only thing in the location autotools chose, but meson chose the same place as all the other stuff installed by the distro. But don't like our chances of "fixing" autotools except by deletion :stuck_out_tongue_winking_eye: But my problem was simpler than that, I just didn't know that an old system install of Geany was earlier in PATH, so was running the wrong version, so old behaviour happened. > Back to the reported problem, another possibility could have been that you > had some old config files in the config directory which contained the #~ - > these legacy config files will stay as they are. It wasn't my problem as I used `-c /tmp/config` so it was clean, but yes, not worth changing such files, if a user has edited it better to not touch it. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3451#issuecomment-1501607247 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/3451/[email protected]>
