On 04/02/2018 07:53 PM, Bruno Haible wrote: > It would make sense for the "rpm runtime dependency detection" to recognize > the /usr/bin/env case as well. In fact, there's already a TODO item in the > source code about this [2]. > > Additionally, this discussion what rpm does or does not do is not related to > gnulib. What rpm does has an impact on the difference between a tarball/source > code meant to be installed by users _from_source_ and a package/binaries meant > to be installed _from_a_distro's_repositories_. This is what rpm is about. > > Whereas gnulib is always installed from a tarball/source code. gnulib does not > have distro-package maintainers. > > Therefore, in gnulib, the most general solution is the best one: > #!/usr/bin/env python > or > #!/usr/bin/env python3 > > The user can then create a symlink as they wish: > ln -s /usr/bin/python3 $HOME/bin/python > Or rely on /etc/alternatives/... > > Bruno > > [2] > https://github.com/rpm-software-management/rpm/blob/master/scripts/script.req
Indeed, that sounded like a quirk. Thanks for the wrap-up. Have a nice day, Berny
