- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Damn, that game’s still going, eh? (/j)
Originally it was called puckman, but they changed it because it would have been too easy to vandalize people’s arch installations
You win!
going full open source 😎
[- - - - - - - - - - - -C o o o o o o o o o]
This is exciting! Can’t wait to kill my install by trying to upgrade!
I mean you don’t really use Arch if you don’t bork it once in a while. :)
That’s a very pleasant word for a horrible experience I keep doing to myself.
You can run pacman on Windows?
It’s called Ms. PacMan over there
Clever.
yes (msys2) except it will never bork your windows install unlike on arch.
Kinda. One of the Linux “wrappers” (I’m a bit tired and can’t think of the correct term here, bear with me) that lets you utilize some Linux utilities on Windows, maybe it was mingw or cygwin, actually uses pacman as their package manager IIRC.
msys2.
Yep that’s the one, thanks!
If anything, i would expect packagekit frontends to break. If you use pacman as intended, you’ll be just fine
The moment I installed it, yay broke. To fix it, if any of you need this: do an ln -s to the .so that is being requested. This allows yay to work again. Use yay to upgrade yay. Finally remove the symbolic link.
Can you do makepkg in the clone of yay PKGBUILD from aur? That seems like a better solution than symlinking…
This is the correct thing to do when it breaks, recompile and link against the new libs. Otherwise you could see funny behaviour.
I did this. And it worked like a charm
That’s how you’re supposed to use AUR, I think. All yay, paru, etc do is make it convenient to do that while also helping with searching and upgrading them.
