On 25-07-2022 08:09:02 -0700, Zac Medico wrote:
> On 7/24/22 23:17, Fabian Groffen wrote:
> > On 24-07-2022 13:58:31 -0700, Zac Medico wrote:
> >> On 7/24/22 12:29, Fabian Groffen wrote:
> >>> Hi,
> >>>
> >>> Quick question, I noticed that portage uses /bin/bash hardcoded in
> >>> shebang of
On 7/24/22 23:17, Fabian Groffen wrote:
On 24-07-2022 13:58:31 -0700, Zac Medico wrote:
On 7/24/22 12:29, Fabian Groffen wrote:
Hi,
Quick question, I noticed that portage uses /bin/bash hardcoded in
shebang of scripts, while it uses /usr/bin/env python for python
executable files.
Is there
On 24-07-2022 13:58:31 -0700, Zac Medico wrote:
> On 7/24/22 12:29, Fabian Groffen wrote:
> > Hi,
> >
> > Quick question, I noticed that portage uses /bin/bash hardcoded in
> > shebang of scripts, while it uses /usr/bin/env python for python
> > executable files.
> >
> > Is there anything
On 7/24/22 12:29, Fabian Groffen wrote:
Hi,
Quick question, I noticed that portage uses /bin/bash hardcoded in
shebang of scripts, while it uses /usr/bin/env python for python
executable files.
Is there anything against using /usr/bin/env bash for shell scripts?
Changing this would help for
Hi,
Quick question, I noticed that portage uses /bin/bash hardcoded in
shebang of scripts, while it uses /usr/bin/env python for python
executable files.
Is there anything against using /usr/bin/env bash for shell scripts?
Changing this would help for Prefix.
Thanks,
Fabian
--
Fabian Groffen
