On 5/17/23 17:35, Genes Lists wrote:
I'm now following how the above helps package maintainers. Quite
^^^
not
The question is basically will "pip --root" continue to work as it does
now if we adopt 668. If not what needs to be changed in PKGBUILD for the
install phase.
thanks
On 5/17/23 16:56, Jude DaShiell wrote:
I found pipenv works well. A package jrnl wouldn't run once built with
pip but does run inside pipenv. This creates a virtual environment for
building and running packages so once jrnl got built doing pipenv run jrnl
runs the program.
I'm now following h
I found pipenv works well. A package jrnl wouldn't run once built with
pip but does run inside pipenv. This creates a virtual environment for
building and running packages so once jrnl got built doing pipenv run jrnl
runs the program.
-- Jude "There are four boxes to be used in
defense of libe
On 5/17/23 11:47, Martin Rys wrote:
Some time ago, PEP 668[1] enabled distributions to mark the python
installation as externally managed by a package manager, thus
preventing pip from breaking the system by either installing packages
to the system or locally in the home folder.
...
[1] https
Some time ago, PEP 668[1] enabled distributions to mark the python
installation as externally managed by a package manager, thus
preventing pip from breaking the system by either installing packages
to the system or locally in the home folder.
Debian has already adopted this[2].
>From my understa
