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
Darshit Shah wrote:
> On a fedora machine, Python 3 is installed by default, but not Python 2. And
> the only binary available is /usr/bin/python3.
It's not only on Fedora. The Python docs themselves ([1], footnote 1) say:
"On Unix, the Python 3.x interpreter is by default not installed with th
Bernhard Voelker wrote:
> FWIW there are discussions [1] in the opposite direction, i.e., to avoid
> /usr/bin/env in the shebang where possible. E.g. in openSUSE there is a
> check for RPM builds which leads to:
>
> pyrenamer.noarch: E: env-script-interpreter (Badness: 9) /usr/bin/pyrenamer
>
On 04/02/2018 10:02 AM, Darshit Shah wrote:
> As you can see here, only Python 3 is installed in the base system. However,
> contrary to expectations, python3 does not provide /usr/bin/python. That
> binary
> is provided by the `python2` package on Fedora. Since python2 is not installed
> by defau
Darshit Shah wrote:
Since Python 3 is the version that is being
specifically targeted, could we please change it to reflect that?
That module doesn't target Python 3 in particular, as far as I can tell; it
should run on either Python 2 or 3.
I dunno, it's pretty weird to have a system that h
Hi,
Sorry for the sparse details. I was confused the first time I saw the issue as
well, but then I forgot to mention all the details.
I was trying to test building GNU Wget2 in a Fedora 27 docker container.
So, the I am talking about Fedora 27 on x86-64. But not the full version, just
what is av
