Am 22.05.2024 um 14:43 schrieb Emmanuel Vadot:
An easier way is to use BINARY_ALIAS= python3=${PYTHON_CMD}
thanks, a maybe even better solution which I found now is:
su -l git -c "cd /usr/local/www/gitlab && yarn config set python
/usr/local/bin/python3.9"
I will update my installation a
On Wed, 22 May 2024 14:10:33 +0300
Gleb Popov wrote:
> On Wed, May 22, 2024 at 2:07?PM Matthias Fechner wrote:
> >
> > What is the recommended why to add python as a runtime dependency that the
> > python binary is available?
>
> We usually patch the software to use pythonXY everywhere. For sh
Am 22.05.2024 um 14:10 schrieb Gleb Popov:
We usually patch the software to use pythonXY everywhere. For shebangs
it can be done via USES=shebangfix and for other cases resort to
patches or REINPLACE_CMD incantations.
this is not possible, at least not directly.
The gitlab port is using yarn to
On Wed, May 22, 2024 at 2:07 PM Matthias Fechner wrote:
>
> What is the recommended why to add python as a runtime dependency that the
> python binary is available?
We usually patch the software to use pythonXY everywhere. For shebangs
it can be done via USES=shebangfix and for other cases resor
Dear all,
I need some help on how to get the python binary and not the python32
binary installed as a runtime dependency.
I tried to use:
USES= python:run
but that only installs the python39 package which only installed the
python30 binary.
If I add:
RUN_DEPENDS= python>=3.9:lang/python
to
