[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Change the python interpretor to use /usr/bin/env python3
From: |
Bernhard Voelker |
Subject: |
Re: Change the python interpretor to use /usr/bin/env python3 |
Date: |
Tue, 3 Apr 2018 08:10:58 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
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