Identify distro packages in `nix --version` #346

New issue

Open

opened 2024-05-23 23:36:54 +00:00 by jade · 5 comments

jade commented

2024-05-23 23:36:54 +00:00

Owner

If Lix comes from a distro package, we would like to know, so that we can make sure that it's not a distro packaging induced bug.

Possible ways to do this:

Require some option in our meson to be set, and then default it to an env-var or so so that our dev shells don't have to deal with it, identifying whose build it is, which we then force downstreams to put into their builds. Or versionSuffix or something.
Detect it ourselves somehow (not really good, since you can have Nix-built Lix on non NixOS)

If Lix comes from a distro package, we would like to know, so that we can make sure that it's not a distro packaging induced bug. Possible ways to do this: - Require some option in our meson to be set, and then default it to an env-var or so so that our dev shells don't have to deal with it, identifying whose build it is, which we then force downstreams to put into their builds. Or versionSuffix or something. - Detect it ourselves somehow (not really good, since you can have Nix-built Lix on non NixOS)

jade added the

Area/build-packaging

label 2024-05-23 23:36:59 +00:00

lunaphied commented

2024-05-23 23:42:29 +00:00

Owner

We've followed this type of issue in general and I think the actual best case here is a process based solution: make people report their distro and how they installed Lix when they report bugs and make it seamless to do so

jade commented

2024-05-24 00:27:40 +00:00

Author

Owner

Maybe nix doctor should print where the executable is, and maybe the host distro. If it's in /usr/bin and it's some distro, obviously it is not our build.

Maybe `nix doctor` should print where the executable is, and maybe the host distro. If it's in /usr/bin and it's some distro, obviously it is not our build.