Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correction to Arch Linux guide #1181

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chowned
Copy link

@chowned chowned commented Dec 6, 2023

Guide was missing the actual command to install the software in arch linux and based distros, it stopped at refreshing databases.
I added 32 bit and 64 bit installer for Arch Linux and squeezed to just one commit as previously requested.

Added 32 bit and 64 bit installer for Arch Linux
@Doomer-Cat
Copy link

Doomer-Cat commented Dec 6, 2023

just adding mangohud + lib32-mangohud to db refresh command and describing would have been sufficient in my opinion

@chowned
Copy link
Author

chowned commented Dec 6, 2023

I followed a previous pull request from here

#1172

@Doomer-Cat
Copy link

Doomer-Cat commented Dec 10, 2023

in my opinion even this would be enough:

Enable multilib in /etc/pacman.conf with sudo
Now refresh databases and install the 32-bit and 64-bit mangohud packages:

sudo pacman -Syy lib32-mangohud mangohud

@flightlessmango
Copy link
Owner

Enable multilib in /etc/pacman.conf with sudo Now refresh databases and install the 32-bit and 64-bit mangohud packages:

sudo pacman -Syy lib32-mangohud mangohud

Something like this is probably better. We get a lot of issues that stems from the user not having 32bit installed, it would be good if users are instructed to install both at the same time

@hashworks
Copy link

sudo pacman -Syy lib32-mangohud mangohud

Please don't force refresh your local package databases (yy) unless they are corrupt. One y is enough.

@chowned
Copy link
Author

chowned commented Feb 4, 2024

I'm not totally agreeing on installing both packages but the user could just install one, what i can say is that i tested on 2 machines with arch linux and a VM on proxmox with manjaro (to try different things) and i got no issue with checking the correct usage with a steam game. So i don't really agree on installing something that is not required, unless a lot of users start to have the same problem.
I agree for not doing double "yy" but it is not something that "breaks" anything, it is just a long operation to refresh all local databases... and i just followed what is currently in the readme.

@flightlessmango
Copy link
Owner

I'm not totally agreeing on installing both packages but the user could just install one

I agree with you, however I'm thinking about pacman -Syy. I believe it's bad practice to update the database without updating the system

@hashworks
Copy link

I'm not totally agreeing on installing both packages but the user could just install one

I agree with you, however I'm thinking about pacman -Syy. I believe it's bad practice to update the database without updating the system

As I said above, running yy is discouraged anyway - it forces a redownload of all package databases and puts unneeded strain on Arch Linux infrastructure. It should only be used to fix broken systems. A single y will check if there are updates and downloads only what's needed.

And yes, in general partial upgrades are unsupported and one should use pacman -S or pacman -Syu unless they know what they are doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants