Eli Schwartz

Alternative suggestion: meson is a fairly popular modern alternative to cmake. It has a reference implementation written in - python, which documents per policy: > Python versions greater than or...

> At the end I'd like to point out that having a complex build system can certainly reduce the number of contributors. CMake is turing-complete, and a whole lotta projects...

> * The file `/src/shell/howdy.sh` and `/src/shell/howdy.csh` contain the variable `HOWDY_LIB` which is not yet initialized > > * During the execution of the post install script, the variable is...

I had already clarified that in an edit, that yes I am in fact referring to both the .cc and the .py files. This does not change what I said.

> but `howdy_gtk` which is another package ... can be configured with `-Dpam-securitydir=/lib/security`, just like this package can be. > For example, Fedora Flatpak based distributions (like Fedora Silverblue or...

> But how it can know where is installed Howdy because it is installed before. Ok, the maintainer of another project must inspect what the maintainer of the main package...

> An update of the main package could break the others An update of the main package to what? The `pam` package changing its security directory? This would be a...

> The problem is not about where is installed the howdy's pam module (and anyway we don't need to know), but about where are `compare.py`, `models/`, `config.ini` and `dlib-data/` Okay,...

What confuses me is, I originally tried this some time ago when the default was `~/.local/share/keybase/fs` and I'm positive it behaved properly... this was back when I originally packaged kbfs...

Also the service file tries to call fusermount on the output of `keybase config get mountdir`, but that may or may not exist, and if it doesn't, kbfs doesn't try...