You know, immutable enterprise systems.
I installed HeliumOS (Almalinux bootc) on a corebooted Chromebook. Works really well, but audio needs to be configured.
The script needs a recent python which is not available there.
Go and rust can be installed for a user only. Is there something similar for python?
Doesn’t pyenv solve?
Plus one for pyenv
Perhaps overkill for your use case, but uv is pretty great. I suppose you could just use it to install a local python and then add it to your path.
This was going to be my recommendation as well.
You might consider trying Miniconda, a version of Anaconda. It installs a local python environment of your choosing at a user level. https://docs.anaconda.com/miniconda/
I Gave it a try on macOS a few days ago because brew and python is a dependencie hell and way to much workarounds to make some scripts to work properly when specific versions of packages are needed…
Miniconda actually made it work fine, without to much hassle. I’m kinda impressed.
I prefer Micromamba since it’s faster at solving environments.
You can also set the solver to use libmamba if you’ve already installed miniconda
You can install the new version of python but leave the system default python as is. You can launch a specific version of python by adding the version number
So python3.12 vs just python3
If you can install nix (you can install it per user) then you can have whatever you want in a temporary shell with nix-shell -p python
nix profile install nixpkgs#python if you want it actually installed
Home manager is also entirely user level I believe and lets you use a declarative config too
I tried to get install instructions for home-manager and they only had them if you are already on nix?
I didnt get it
I’d try installing just regular nix (package manager, not operating system) rather than home manager, that’s what I do on by Debian pi
There’s an install script on their website that does it all for you
Nice! Yes I will do that. What is the difference between the 2?
Careful, there’s three different terms in the mix here:
NixOS: an entire operating system, you don’t need this.
nix: the nix package manager. This is what you’ll need to install. look for single user install in the instructions.
home-manager: a module for nix. It’s aim is to allow declarative configuration of a users’ home configuration (and allow easier per-user install of packages on a global nix install).
If you want to go down the nix route, which I would recommend if you enjoy tinkering and having fine control over your system, you should start with installing nix. With that, you can already setup a shell that has the newest version of python available.
Going beyond that, I can link you some more resources, if you want c:
So “nix install” means placing a nix binary somewhere in my user $PATH?
Home-manager > nix profile
Also, nix-shell is supposed to be used for debugging, and nix shell/run/develop for using packages without installing them
Source on the second statement? My understanding was that nix-shell is legacy for systems without flakes and nix-command enabled, and are being replaced by nix shell/run/develop
Interesting, didn’t know the history of the command. But that post confirms my understanding, that nix shell/develop are the new replacements for nix-shell, with nix shell for temporary package installs and nix develop for debugging and developing
As far as I understand, they’re not replacements in the same way nix profile replaces nix-env. They seem to serve a different purpose, but I don’t know enough to say for certain.
of course they’re not a drop-in replacement, as the cli is getting a major redesign, but as per your source
nix shell and nix develop are still experimental, so nix-shell is sticking around despite doing the same thing
it seems like they are made to fulfill the same purpose
Does home manager work standalone without having nix first? I’ve never installed it on non-nixos
Nix shell is absolutely for running packages without installing them it literally tells you to do that in the terminal hint
Nix run iirc only works with flakes
No, it builds on top of nix. But it seems like the only real option for declarative package management.
Nix shell and nix-shell are different commands
https://discourse.nixos.org/t/nix-shell-nix-shell-and-nix-develop/25964/4
Nix run iirc only works with flakes
So does nix shell
nix shell -p works without flakes enabled
$ nix shell -p python error: unrecognised flag '-p' Try 'nix --help' for more information.Sorry I meant nix-shell -p, I didn’t read your original comment properly apparently
It’s definitely an option as op wants to run one script from the sounds of it, nix-shell not nix shell is perfect for that
It’s a bit needlessly confusing that there are two entirely separate commands with the same name and thought you were talking about the original one
You should be able to have multiple versions with an environment manager, maybe customize your shell profile to alias python to the one you want and the other users can alias to the one they want. I’m sure there’s a better way, but I strongly dislike python every time I try to learn it because Perl was the first language I learned, ruining me for strongly opinionated languages.
Compile it, install it to your ~/bin.
~/.local/bin;)But yes, great idea.
I found a script online that installed the tar archive. For some reason that version of python still wasnt used, and invoking it with
python3.12.6or something didnt do anything~/bin is the real directory for UNIX.
It is?
Can you use pyenv for the script?
@boredsquirrel
One solution could be to install uv for a single user, and use that to install and run a Python interpreter.Have you considered using pipx + poetry?
Maybe a tooling manager like mise or asdf.
Can you put it in the ~/bin or something and modify the $path to go there first?
~/.local/binyou mean?;)
Yes I tried that, and got like 6 different solutions to do this so I will see :)
Yes . Local/bin, good looking out.
Does your which program name report the right one?
Not yet fixed, no motivation
I currently use this workaround ;)
Tbh I would probably never fix it if that worked. What’s a little dongle between friends.
Audio configuration sounds like a shell task. Why does it need Python? Is this script in any way an official part of the OS?
No not a part of the OS and als no idea why they used python, that script is full of crazy functions so may be needed.
I translated the python 3.12 to 3.9 using ChatGPT lol, as even after installing up-to-date python and placing it in my home $PATH the script threw errors.
I think it worked, but there is an issue with my atomic system, so I likely need to build an RPM for the changes or use a different command for akmods or package the kernel myself or whatever.
Ah, I see. Well I’m glad it worked!
🤣 damn I would’ve been looking for a new image to flash at that point.
I’m glad chatGPT didn’t brick your system.
Where’d you get the audio setup script?
I am on a Chromebook and that is a recommended script. There are really just a few functions in python 3.11 that are missing in 3.9
This script? https://github.com/WeirdTreeThing/chromebook-linux-audio
I’m not familiar with bootc based systems but it looks like you could hack up the container spec here: https://codeberg.org/HeliumOS/bootc to build heliumOS with those changes. You would then use something like
bootc switch ...to use it.(Add a line in the docker file to install newer python and run the audio script. I’m not sure if the script requires changes for this.)
I could be way off base with this idea, I’m not sure how heliumOS expects users to install packages.
You may also be able to run the latest python docker image to run the script, but the way this script modifies system files shouldn’t work on an immutable system.
Haha thanks for the idea!
That actually makes a lot of sense. The image building simply should be really easy if you can just pull the already made image and just add the file.
There is an example to install newer python, do something and uninstall it again (which I wouldnt do).
Thanks, I will try to do that. I think HeliumOS has a future as a ChromeOS alternative
Not familiar with HeliumOS specifically, but for a generic atomic distro I would try layering Python temporarily, and then getting rid of it when you’re done.
I see from the github ticket you need 3.10 .
There’s an EPEL clone, apparently, that bundles a python3.10 package.
MAYBE this is your process:
yum* install dnf-plugins-core yum config-manager --add-repo=https://pkgs.dyn.su/el9/base/x86_64/ yum install python3.10Then use it like
/usr/bin/python3.10. Remove it and the repo after.*I avoid using DidNotFinish(dnf) even though I know it’s an alias.
Loooool
I thought there was no rpm-ostree but there is.
Well, lets layer some stuff!
