There are many things that can stop me from running a program but what distro it is is not one of them.
Seriously, look at what the pkgbuild is doing on Arch and replicate it by hand on your distro of choice. That’s all a pkgbuild is: a simple bash installation script.
have fun translating all the package names!
Distrobox is your friend. Me, I like an immutable OS (kinoite) but I still want the AUR…
distrobox-create --name arch --image archlinux:latest distrobox enter arch install yay as normal yay -S vscodium distrobox-export --app vscodium yay exa distrobox-export --bin /usr/sbin/exa exit [back to kinoite] exa [works] vscodium [works, has icon in application launcher]Try it, you might like it !
Ooh, a fellow Kinoite user!
I’m actually aware of Distrobox, but the thing I had in mind was for managing gaming wheel drivers, so I don’t think it’d work on distrobox. It’s not really that big of a deal honestly, I just made this meme to poke fun at it ^^’
Fair enough, but CUDA stuff works surprisingly well for e.g., I’d give it a go if it’s just USB.
Kinoite Represent!
Joke’s on you. I use Arch BTW
You beat me to it! I also use Arch BTW.
I use Arch BTW.
But also I feel like handing a AUR manager to a person is like giving them a block of C4 and a detonator and saying “good luck”
Stupidly powerful, but you can blow your hand or foot off in a second if you’re not aware
You Linux people are funny.
I just download the Windows versions and run them with Wine.
I don’t understand any of this, my windows install is on a 120GB SSD, it’s full now and I can’t update my graphics driver.
I’m a noob, isn’t every (open source) program aviable for every distribution if you compile it from source? It’s all Linux in the end (i never compiled a program from source, so I don’t know if it’s easy at all)
Some programs may use libraries or tools specific to a distributions package manager. For example, yay, an AUR helper/pacman wrapper. You would have a very hard time getting it to work on Debian.
Other programs might only include build scripts for a distro specific build system. For example, a program might skip using a Makefile, and do everything in the Arch-specific PKGBUILD.
Generally though, most software uses a standard cross-distro (or even OS) build system. In this case, compiling from source would be an option on any distro. The program might still only be packaged for Arch/NixOS/Gentoo (or others), as it is a very simple process to do so.
Usually the only tricky part of compiling from source is tracking down dependencies. The package manager does that for you normally but you’re not using the package manager when compiling from scratch. The actual building (even compiling a kernel) isn’t all that complicated.
distrobox for most cases should be fine…
./configure && make && sudo make installGet off my lawn.
I copy pasted this in my terminal and got an error. Apparently my Linux doesn’t know
&&I can’t imagine that’s true.
It automatically converted the code, I edited the comment
I use arch btw
Can’t you just use it though distrobox and podman?
Not as easy or as convenient as
yay -Sy appnameit actually is, you just append the distrobox command before it
distrobox enter arch -- yay -Sy appnameA simple
yay -Syfrom Arch btw takes less computing power and doesn’t depend on an external dependency.Any reason not to just use
yay? That’s an alias foryay -Syu, which in and of itself, at least if I understood it correctly, is basically justpacman -Syuand from what I’ve read on the arch wiki-Syis heavily discouraged.yayin the example was used to install an AUR; not to update the system which is what you are talking about. And the discouragement you speak of-Syapplies only to pacman upgrades, not AUR helpers. The only reason theyis discouraged in the wiki when installing a package is because it fetches updated data from the repos which might lag the rest of the system (and potentially the resulting dependencies if any). Most of the time it is not a concern as most (quality) software is made to be backwards compatible anyway.
But then you stuck with arch. I’ve never had any software that wasn’t a flatpak or in the Debian repos. I use Fedora.
I would say you are stuck on Fedora too, what is your point?
I’ve never had any software that wasn’t a flatpak or in the Debian repos.
There are quite a number of them, hence the reason for OP’s meme.
Really? I honestly have never had that problem. Can you name a few? (I’m completely serious. Don’t take this as sarcasm)
There are so many software devs that package AURs because Arch has made it easy for them to do so. No need to give examples if you are totally fine with your brand of distro.
But whether you’ll hit the minor snag OP memes about depends on your software needs.
But then your installing it locally. The benefit to containers is they can be deleted.
Also Arch is a unstable mess and requires updates way to frequently
I’ve been using Arch for over a decade now. On a laptop, desktop, VPS and now it’s also driving Steam OS on the Deck. I had very little problems with it compared to our Ubuntu setups at work that randomly break on updates. Ubuntu is not as bad as it used to be but from my experience (i.e. the way I use it), Arch has been more stable and reliable.
I have also had issues with Ubuntu. I just stick with Debian because I don’t have to touch it for years.
Can you do the same with Arch? Also why do you need newer packages on a server? (I’m taking about the VPS)
No, you need to do system maintenance on Arch at least once a year if you don’t do it after each update. You need to merge configs (I love etc-upgrade from gentoo for this) and find and delete orphaned packages left behind by the rolling release that are still on your system.
I haven’t tried not touching it for years to be honest. Longest period without a reboot was something between half a year and a year and it worked without a problem. Check the Arch website, breaking changes or manual interventions are very rare nowadays. There’s just one thing you have to do if you start an update after a long time: make sure to update the keyring first or pacman will exit with an error. That’s also mentioned in the wiki.
I installed Arch on my server because:
- I know it very well.
- The base system is tiny. Fewer packages = fewer problems. Everything else is in Podman containers anyway.
- It’s very flexible. I have a customized encrypted rootfs which needs to be unlocked through SSH, not a very common thing I guess.
But then your installing it locally. The benefit to containers is they can be deleted.
This does not make any sense in this context. Or anywhere else if you want to get real pedantic.
Also Arch is a unstable mess and requires updates way to frequently
Arch can be unstable at times but that’s part of the deal as is with any distro you’ll install and use over time. Requiring updates frequently is also not a valid argument against Arch as you can choose when to update.
Arch ships to new of packages for my comfort. This leads to breakages if you don’t read the update notes. I want my system to stay updated automatically and Arch causes to many headaches.
Software updates can potentially cause issues in general. This situation is not unique to Arch.
There’s nothing wrong with a rolling release model where you get newer software that’s closer to upstream. In most cases, you get security updates faster and in some instances you get bug fixes & new features from upstream that will take weeks if not months to hit “stable” distros.
That’s fine if you like that kind of thing. However it isn’t for everyone
Arch ships
totoo new of packages for my comfort.Sorry to be a grammar nazi but that’s the second time and it annoys some of us. It’s literally a different word with a different meaning!
This is not a problem, I use garuda btw.
…or nixpkgs they have the most packages of any distro (although, I don’t know if they also count all the language specific libs like from pypi, npm, crates, etc.)
You can install their package manager on your distro of choice
Yes, most packages are auto-generated from those. When it comes to manually generated packages AUR should still be #1. Not that I ever missed any packages in nixpkgs…
Just do whatever the package file says.
Same. Yesterday, I found Vulkan drivers for virtual machines (vulkan-virtio) , but it’s packaged only for archlinux. And I gave up trying to build from source yesterday.
or only as appimage
Skill issue (I use arch btw), all jokes aside maybe try distrobox it should work perfectly
