Would removing the previous user cause me to be locked out of doing any sudo task? In addition, would mixing in nix packages interfere with mandriva? For example, yazi straight up doesn’t have a package here, which is perfectly fine. It is a niche package. Nix has it, so can I use that without it messing up the system. Or for something’s even more critical like ROCm drivers or hyperland since it has official support in nix.
If this is going too off-topic for this, that is understandable.
Probably, and we wouldn’t support this.
From the site I linked earlier. I can understand if you ignored it:
https://abf.openmandriva.org/openmandriva/yazi/build_lists
We also have hyprland, but I think you would probably prefer to just use NixOS.
Understandable that it’s not suported, The link you send just opens a blank page,and in terms of nix… I would really rather not, As much as I like elbow grease on file learning to use nix is worthless since it can’t be used anywhere else.
Update:
I saw teh change you amde to the link and saw yazi, it’s in cooker which is great news, because taht means it’s on the way. Just for sake of knowledge, how unstable is cooker?
It had to be edited. Try it again.
I saw it. The reason I didn’t see it on my end when searching the repo was because I was on rolling, not cooker. How unstable do you think cooker is? If it’s as stable as openSUSE tumbleweed, then we are golden. If not, I can just wait.
Cooker is not as stable as Tumbleweed. Don’t do it. 
you can just grab the .rpm files on abf and install them manually (not sure if this is something we’re supposed to do but I would guess it’s still better than to just switch to cooker)
abf is kind of unintuitive you have to click the build number to see the files (and there are multiple build numbers depending on the architecture)
for ryzen CPUs Build list - Project openmandriva/yazi - Openmandriva ABF
for other x64 CPUs Build list - Project openmandriva/yazi - Openmandriva ABF
The problem you may run into is dependency version support being lower. Probably not on a package like this. It should work. As far as Cooker being stable or not, it depends on how bad you need to update. You would have to watch builds on abf more closely before performing a dsync. If the DE, kernel, or browser are being built currently and any of the packages needed to make it work have build errors, you just don’t update yet.
I use cooker on my gaming PC, less problems that I encountered with openSUSE or Ubuntu.
Are you on x86_64 or znver1 ? If you want yazi and are willing to test it, you can grab it with a one time enable of the repo. It doesn’t add the repo and put you into cooker.
sudo dnf install --enablerepo=cooker-znver1 yazi --refresh
or
sudo dnf install --enablerepo=cooker-x86_64 yazi --refresh
I have it running on mine and I am still on ROME. I have to admit. It looks really good with our OMDark color scheme.
You don’t have to switch when you use the command I showed. It enables the one time shot to grab the files from the cooker repos.
Just a warning and I know @zeroability will back this up. If you run cooker, you better be in the cooker chat, so you can ask before doing an update. Do not just switch over and think you are good to go. I am in that room and I constantly see developers asking, “Is it safe to update right now?”
For a newcomer to OpenMandriva using cooker definitely IS NOT a good idea.
Cooker is the development branch and is expected to break any time.
Only developers and very advanced users (who do know how to sort out of issues) should install cooker.
That disclaimer made very clear, what’s the problem now?
As far as I can see the original post question has been exhaustively answered.
The user believed that install packages was not done as system admin (root) but turned out that it just was a misunderstanding (sudo=1st created user/wheel password, su=root password).
Well, the user still needs a way to make it ask for the Root password and not ask for the User password, because root has a complicated password.
How do I do system wide installs? - #22 by YAR_Oracool
Most of us use the same password. He does not, and I can see why.
Atm moment I’m tackling Nvidia issues because ofcource I am and also there is no prime select package. Nvidia driver installation breaks the welcome program on x11 but in both way land and x11 it says Failed unit detected: “nvidiax2dsettingsx2dload@aurostart.service”
Sorry for the late reply, I got hit with a reply cap.
Fair enough, That’s why I never bothered with arch. The question is half answered. The packages are being installed system-wide but still asks for user, which I’m gonna tackle on a bit later since I’m busy with my capstone project at the moment.
I think if you remove your user from the wheel group such user will lose the privileges.
Not 100% sure though, usually I happen to have to do the opposite. Better if you wait for someone who knows better.
Well… The system is new, I can just do it, and it breaks the system just reinstall but I am having Nvidia optimus issues which seem to not have a solution here specifically.
So I wanted to switch to openMandriva, but there are few critical packages missing. I guess I have to wait it out until those packages are there. Like Nvidia prime. Thank you all for your help, it taught me how the permission system works.
Please file a ticket at Issue Tracker > Package request
https://github.com/OpenMandrivaAssociation/distribution/issues/new/choose
We can’t provide anything if we don’t know that users need them.
So we ended up getting something good regardless 
It was not time wasted.
Feel free to come back any time, or stay around and hold on for a bit more.
