Timeline for NixOS service systemd unit's $PATH does not contain expected dependency
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 28, 2021 at 20:33 | vote | accept | Chris Stryczynski | ||
| Jul 11, 2021 at 18:55 | history | edited | Robert Hensing | CC BY-SA 4.0 | edited title |
| Jul 11, 2021 at 18:54 | answer | added | Robert Hensing | timeline score: 4 | |
| Jul 10, 2021 at 19:33 | comment | added | Charles Duffy | The usual approach is for the derivation for that app to itself include a wrapper that puts ffmpeg in its PATH before starting the real/underlying executable. | |
| Jul 10, 2021 at 19:15 | answer | added | Chris Stryczynski | timeline score: 5 | |
| Jul 10, 2021 at 19:09 | comment | added | Chris Stryczynski | Is there an alternative to that? The question is a simplified example. Right now I have a built app that relies on ffmpeg being accessible in the PATH. | |
| Jul 10, 2021 at 19:07 | comment | added | Charles Duffy | (Same reasoning behind nix best practices using rpath when dynamically linking instead of trying to build a LD_LIBRARY_PATH to dependencies) | |
| Jul 10, 2021 at 19:06 | comment | added | Charles Duffy | Call ${pkgs.ffmpeg-full}/bin/ffmpeg --help. Best practice is not to rely on PATH lookups unnecessarily. | |
| Jul 10, 2021 at 19:01 | history | edited | Chris Stryczynski | CC BY-SA 4.0 | edited title |
| Jul 10, 2021 at 18:51 | history | asked | Chris Stryczynski | CC BY-SA 4.0 |