Missing install instructions for pipenv on openSUSE Tumbleweed
Hi!
I'm reporting this here instead of bugs.kde.org because I didn't find the kde-builder project there.
The README says pip install
should be used on openSUSE Tumbleweed to install pipenv because it's not in the repositories, but I get:
sudo pip install pipenv error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try
zypper install python311-xyz, where xyz is the package
you are trying to install.
If you wish to install a non-rpm packaged Python package,
create a virtual environment using python3.11 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip.
If you wish to install a non-rpm packaged Python application,
it may be easiest to use `pipx install xyz`, which will manage a
virtual environment for you. Install pipx via `zypper install python311-pipx` .
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Easy install instructions on openSUSE Tumbleweed would be appreciated :-)
More generally, in case this is not already planned, kdesrc-build is quite nice in that you can just git clone https://invent.kde.org/sdk/kdesrc-build.git && cd kdesrc-build && ./kdesrc-build --initial-setup
. Since kde-builder
is supposed to be a drop in replacement, It would be amazing if git clone https://invent.kde.org/ashark/kde-builder.git && cd kde-builder && ./kde-builder --initial-setup
was able to take care of all this on common distros: installing the right version of python, installing pipenv, running pipenv install
, and create the ~/bin/kde-builder
wrapper script. btw, this should probably be ~/.local/bin/
, or even perhaps the wrapper script should just be at the root of the repository and --initial-setup
updates the shell configuration so the wrapper script can be found in path, like kdesrc-build does.
It's very usual that Python projects tell users about virtualenvs and all this stuff, but this seems to be specific to Python and I never found this very user-friendly in the first place. The tooling is also never quite the same. All this should be hidden away, users don't need to know all this unless they want to actually contribute to kde-builder.
edit: Even more generally: I was not even aware kdesrc-build was written in Perl and this was a feature :-)
In any case, I'm sure this Python rewrite is needed, thanks for all this tedious but necessary work!