▲ 3 ▼ What is your favorite package manager? (feddit.de) submitted 3 years ago by iloverocks@feddit.de to c/unix@sh.itjust.works 7 comments fedilink hide all child comments My favorite is pacman because it is fast af but it has really weird syntax's
[–] mrmanager@lemmy.today 0 points 3 years ago (2 children) I use yay, it's pacman with AUR support. :) permalink fedilink source hideshow 4 child comments replies: [–] Dathknight@feddit.de 1 point 3 years ago came here to post this. Also it always feels like I'm cheering for my system. :D permalink fedilink source parent [–] chaorace@lemmy.sdf.org 0 points 3 years ago* (last edited 3 years ago) (1 child) FYI: yay is no longer maintained (Untrue! See response here). Use paru instead Consider paru as an alternative option; it's written in Rust and has better version tracking for *-git packages (won't miss upgrades if the AUR version isn't tracked, won't do pointless upgrades if the AUR version changes but HEAD remains unchanged) permalink fedilink source parent hideshow 2 child comments replies: [–] gizmonicus@sh.itjust.works 0 points 3 years ago (1 child) The latest release of yay was 3 weeks ago. Where are you seeing that it's not maintained anymore? permalink fedilink source parent hideshow 2 child comments replies: [–] chaorace@lemmy.sdf.org 1 point 3 years ago (1 child) Huh! I appear to have fallen victim to misinformation. I stand corrected and I apologize for not properly confirm such a strong claim before repeating it like that. I suppose a more accurate way to put it is that yay has been slower to adopt new features (e.g.: yay#336 vs paru#260), but otherwise remains a current and well-maintained piece of software. permalink fedilink source parent hideshow 2 child comments replies: [–] gizmonicus@sh.itjust.works 1 point 3 years ago I was about to throw my computer out the window when you said that because I literally just implemented a bunch of ansible playbooks using yay to configure my machines and after yogurt et. al. being abandoned, I couldn't take another change. Not yet. I'll check out paru at some point though. permalink fedilink source parent
[–] Dathknight@feddit.de 1 point 3 years ago came here to post this. Also it always feels like I'm cheering for my system. :D permalink fedilink source parent
[–] chaorace@lemmy.sdf.org 0 points 3 years ago* (last edited 3 years ago) (1 child) FYI: yay is no longer maintained (Untrue! See response here). Use paru instead Consider paru as an alternative option; it's written in Rust and has better version tracking for *-git packages (won't miss upgrades if the AUR version isn't tracked, won't do pointless upgrades if the AUR version changes but HEAD remains unchanged) permalink fedilink source parent hideshow 2 child comments replies: [–] gizmonicus@sh.itjust.works 0 points 3 years ago (1 child) The latest release of yay was 3 weeks ago. Where are you seeing that it's not maintained anymore? permalink fedilink source parent hideshow 2 child comments replies: [–] chaorace@lemmy.sdf.org 1 point 3 years ago (1 child) Huh! I appear to have fallen victim to misinformation. I stand corrected and I apologize for not properly confirm such a strong claim before repeating it like that. I suppose a more accurate way to put it is that yay has been slower to adopt new features (e.g.: yay#336 vs paru#260), but otherwise remains a current and well-maintained piece of software. permalink fedilink source parent hideshow 2 child comments replies: [–] gizmonicus@sh.itjust.works 1 point 3 years ago I was about to throw my computer out the window when you said that because I literally just implemented a bunch of ansible playbooks using yay to configure my machines and after yogurt et. al. being abandoned, I couldn't take another change. Not yet. I'll check out paru at some point though. permalink fedilink source parent
[–] gizmonicus@sh.itjust.works 0 points 3 years ago (1 child) The latest release of yay was 3 weeks ago. Where are you seeing that it's not maintained anymore? permalink fedilink source parent hideshow 2 child comments replies: [–] chaorace@lemmy.sdf.org 1 point 3 years ago (1 child) Huh! I appear to have fallen victim to misinformation. I stand corrected and I apologize for not properly confirm such a strong claim before repeating it like that. I suppose a more accurate way to put it is that yay has been slower to adopt new features (e.g.: yay#336 vs paru#260), but otherwise remains a current and well-maintained piece of software. permalink fedilink source parent hideshow 2 child comments replies: [–] gizmonicus@sh.itjust.works 1 point 3 years ago I was about to throw my computer out the window when you said that because I literally just implemented a bunch of ansible playbooks using yay to configure my machines and after yogurt et. al. being abandoned, I couldn't take another change. Not yet. I'll check out paru at some point though. permalink fedilink source parent
[–] chaorace@lemmy.sdf.org 1 point 3 years ago (1 child) Huh! I appear to have fallen victim to misinformation. I stand corrected and I apologize for not properly confirm such a strong claim before repeating it like that. I suppose a more accurate way to put it is that yay has been slower to adopt new features (e.g.: yay#336 vs paru#260), but otherwise remains a current and well-maintained piece of software. permalink fedilink source parent hideshow 2 child comments replies: [–] gizmonicus@sh.itjust.works 1 point 3 years ago I was about to throw my computer out the window when you said that because I literally just implemented a bunch of ansible playbooks using yay to configure my machines and after yogurt et. al. being abandoned, I couldn't take another change. Not yet. I'll check out paru at some point though. permalink fedilink source parent
[–] gizmonicus@sh.itjust.works 1 point 3 years ago I was about to throw my computer out the window when you said that because I literally just implemented a bunch of ansible playbooks using yay to configure my machines and after yogurt et. al. being abandoned, I couldn't take another change. Not yet. I'll check out paru at some point though. permalink fedilink source parent