Gimme the repo and I'll get it to compile on Arch, latest testing packages as per 2025-10-20T22:12:00 on repo.30p87.de/archlinux
this post was submitted on 20 Oct 2025
924 points (98.7% liked)
linuxmemes
27973 readers
1594 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
What colors are your thigh highs?
Black-white, preferably pink-white. I overcompensate a lot for boymoding.
It's too funny to me that Arch of all distributions attracts the thigh /Unix socks crowd (for lack of better word). Nothing about Arch stands out for me in that regard, there's no social statement or anything, and when I was more active in the community, it wasn't known for that.
I was deep enough into Arch to run my own private repository using aurutils, but no thighs :(
I have them but I use Debian mostly.
load more comments
(1 replies)
mine are pink white too :D
Both of these two cases are why Flatpaks are so attractive.
Flatpaks are better than Snaps, but properly maintained dependency trees and SBOMs are best, by a wide margin.
PopOS fucked me up with flatpaks
Gateway drug
They are extremely effective at preventing PackageKit updates on my steam deck
I'm going to be honest to you, I prefer appimages.
I respect your wrong opinion
I rarely encounter them. But they usually work when I do. But, ugh, they're just kinda gross. Like, is this a .exe? No thank you. Don't give me windows trauma.
load more comments
(3 replies)
load more comments
(1 replies)
plus that extra defense-in-depth layer of a sandbox
load more comments
(4 replies)
You didnt waste those hours, you learned something.
Nothing that useful, apart from learning again that reading error messages properly can save you much pain.
Thatβs a useful lesson to have stick
Last week was the first time I think I've ever got a random Internet tarball to configure, make and make install. Program even did what it was supposed to too. I was amazed.
The last picture in the meme always bothered me, because the sequence doesn't make any sense physically. (Popping the rake from mid air and doing the wrong flip and such)
So, I went on to find the sequence that I believe it was drawn from.
you think the sequence doesn't make physical sense, but skateboarding on a rake is fine?
It's like flying on a broom. Perfectly logical.
load more comments
(1 replies)
I honestly can't remember the last time I've come across a package that I needed that so obscure that it wasn't found somewhere as at the very least an appimage, if not a flatpak. I haven't had to build from source in I don't even know how many years now.
What? Its something I do quite regularly.
Try making music on Linux. You'll be compiling obscure shit and tweaking configs all the time.
True. But I was coming at if from the perspective of an every day user coming from Windows. email, word processing, internet, etc... Even gaming and photo editing.
The more professional the needed software gets, of course the more obscure it gets.
load more comments
(2 replies)
so true
and yeah i can confirm i've been using linux for 7 years...
God bless flatpak for these cases
*Laughs in Nix
*accidentally uninstalls python base package trying to fix dependency conflicts in apt
As a non IT person I find Linux way better for installing software. The sort of apps non IT people use. The Software store has most of what I need. There rest I install the Windows way. From a website. Apps with a Linux version almost always detect and offer a Linux button to click to install. I wouldn't know what to do if that didn't work. Ditch that application I guess. My distros are pretty standard. Not hacked about. My apps are not too weird. I've been doing it this way for 14+ years. Never needed the CLI either.
LMAO, back in my Slackware days (3.4, 3.6, 4.0, 7.0), If I had to build from source, which was most things, step1: ./configure step2: install the missing package step3: goto step1 until no missing packages identified step4: make step5: make install
Sometimes my packages were too old, So I would just go to step1 for each package that also needed to be newer. I'm not even a Linux Expert, and I definitely wasn't a Linux Expert then. All the building from source helps me jump into software projects and become productive real quick though.
When the dependencies need dependencies and then those dependencies need dependencies, the rabbit hole is endless!
load more comments
(2 replies)
Bruh just use nix, flatpak or appimage πΏ (we don't talk about snaps)
"Just use Flatpak."
"But that will use 2GB when a system package will use 34MB."
"Duh, it's not 2GB total. Flatpaks share dependencies."
"I don't have any other Flatpaks on my system."
"..."
"..."
"OK, so it'll be 2GB. Your next one will be smaller, though."
"If I install one and if it shares any dependencies with the first one."
"Pff. You're just a hater."
"Yeah, I hate that something that should be small is using 2GB of space."
βJust use Flatpak.β
βBut that will use 2GB when a system package will use 34MB. Yeah, I hate that something that should be small is using 2GB of space.β
"The space consumption isn't my preference either, but I'd rather be using the app than fighting dependencies. I wish you luck with your dependency chain then."
load more comments
(2 replies)
load more comments
(2 replies)
load more comments
(1 replies)
More like:
No system package -> installing from user repos -> appimage -> flatpak -> creating your own package -> using a VM with a distro that has the package -> not installing package
If after that you still don't have it, ~~it wasn't meant to be~~ it's probably just not very good software.
load more comments
(1 replies)
This is why you use Arch/Nix because the package is likely in their repos.
The software probably still won't work, but you can waste more time on it.
All these different package manager systems.
I think we just need to consolidate and make a standard one
load more comments
(1 replies)
view more: next βΊ