Hi Kurome, Kurome <hunt31...@gmail.com> writes:
> Hi Guix, > > I see search-input-file and search-input-directory used to specify file paths > of > input packages, like this: > > (search-input-file inputs "bin/foo") > > From my observation, this can also be rewritten as: > > (string-append #$(this-package-input "package-foo") "/bin/foo") > > #$(file-append (this-package-input "package-foo") "/bin/foo") In general, I've found search-input-file to currently be superior to using this-package-input in gexp references, because these gexp references are not currently automatically fixed when using package input rewriting. So if you used something like #$(this-package-native-input "python2") and changed python2 to python3 in the *native inputs* of an inherited variant, the variant would still refer to python2 its gexp reference was used in a phase. So, I currently prefer search-input-file, using #$(this-package-input ...) only where search-input-file would be ambiguous. This could change if we improve the way gexps and handled in phases. -- Thanks, Maxim
