Florian schreef op za 15-01-2022 om 15:19 [+0000]: > [...] > As I see major problems f.e. with QT applications, that seem related to > not setting search paths, a proposal of mine for the future would be to improve/ > actually introduce good documentation to the search-patch > variables (and their relationship to profiles and propagated inputs) About documentation, you might be interested in . > but > maybe simplify setting a search-path correspanding to a more distinct > group of programs. I could imagine this as something like a search-path > "type", working out like this: > (package > ... > (native-search-paths > (list > (search-path-specification > (type terminal-emulator)) > ...) > ) > at first this would just be the same as the code added to foot, but it > could be refined (people might be able to see overlaps, and integrate > some filtering or other optimization for a specific group. Also you could maybe eventually say "install a > package but without these search-paths"). For groups like qt plugins, > it could maybe be included in the qt-wrap functionalities to look for > the paths where plugins are installed and add the corresponding search paths automatically. Not sure what you mean here, when building a package it is unknown what plug-ins will be used in advance. The point of search paths is having some kind of extensibility, setting the search path environment variables in qt-wrap would undo that. Greetings, Maxime.