Guys I downloaded the github link, and it won't launch as an app, what do? :(
/j
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo
in Windows.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.
Guys I downloaded the github link, and it won't launch as an app, what do? :(
/j
You could add '.exe' at the end. It will definitely not work, but you can still do it for a laugh anyways ;)
Wine: wtf is this shit?
Time for an angry bug report.
Wine could probably run it
Are you a vibe coder?
I have standards unfortunately
Have you tried downloading the AUR? Oh, it's not available in the AUR? What about the flat pack? The package name changed, but it's not available there either. It's an app image, but to get it to work you're going to need to switch your Nvidia drivers to DKMS. OK... So that didn't work, have you tried reinstalling dracut and ffmpeg?
My favourite of course is "just dual boot"
The solution to every issue x3
Dual booting is just using containers on bare metal.
Real
(γΰ² ηΰ² )γ彑β»ββ»
Now you're just being silly. Everyone knows that Linux is better than Winblow$$$ because all your programs are available from your app store, and can be installed with a few clicks. You never have to go hunting for random downloads again! π
If it's not in the AUR, it doesn't have more than 10 users in the world.
you gotta click on the blue e on your desktop
You guys have stuff on your desktop?
OMG I thought I'd never find a reference to this in the wild! I love the website is down
Based arrangement
I prefer to keep my desktop completely empty tho x3
Dependencies:
Old ass library version from 2004
apt/dnf/pacman: package not found
library package was last available 15 years ago before it was dropped to move to the next legacy version
App package was available right up until last year until it was dropped for development inactivity
Absolutely no one has a compiled version of old ass library
Attempting to compile old ass library results in 30 other old ass package dependencies
How in the actual world was the maintainer compiling this up to last year
It worked on their machine
They have old/orphaned dependencies on their machine. It's hanging on a by thread. They have no idea the packages have disappeared years ago. The house of cards is a bit flip away from collapsing.
Hahah I say this all the time.
Why docker was created be like
Does docker solve this problem?
Ah the Linux help desk where you get helpful directions like "You have a problem with your dual monitor setup in your naively installed Ubuntu setup? Have you considered installing a rust micro kernel from an abandoned GitHub repo? After cherry picking some patches from a mailinglist? Also boon plep Ubuntu looser."
Why even use releases? Everyone can build everything for themselves. 'Normal Users' are just lazy, everyone wants to know how every piece of software is built for their system, it's not like they have other stuff to do.
I thought that was what Gentoo was doing, but they have far more binary packages nowadays than I thought they'd ever get.
Which you still need to specifically specify. By default everything still has to be compiled.
That's good then. :)
llvm, clang are packages I give 0 fucks about, but take a significant part of my updates. I never really got around to it, but I will try to make them binary downloads instead of building that shit. Like I understand gcc, but have 0 interest in llvm, and can't have firefox without it.. smh
yay
There is a 99% chance it's in there, and there is an 80% chance it uses the latest version/git HEAD
Yay?
yay
, a utility to access the AUR, where users share build scripts instead of binaries. It's just one step above curl | sudo sh
in terms of security.
Except it automates the steps you'd have to take to inspect and edit the script, if needed. Also, PKGBUILDs are much nicer to read than just plain install scripts. And, of course, it actually builds a package, which is then installed, so it's not only tracked but can be updated like the rest of the system.
To be fair, that's why they said
in terms of security.
I'd say that yay encourages checking the PKGBUILD or its diff more than the average "curl xy | sudo sh" instruction, but considering most people see yay just as yet another package manager, instead of an AUR helper, that's probably true for most people
I don't think the aur can switch the delivered script whether you are piping it into sh or not.
I don't care for this mentality. I understand constant questions must get old for developers/contributors but the mentality that people should compile from the source is not conducive to growing FOSS. It is, however, potentially conducive to laziness from the devs. "Eh, why should I spend time releasing compiled builds? Let the plebs compile themselves."
Devs don't usually package for specific distros unless it's a generic format like Appimage that can just be downloaded. Distro maintainers need to get it into the format their package manager uses and update the list to make it available.
Nobody likes to figure out dependencies. And C++ template errors are sometimes completely crazy.
Unless it's a JavaScript app which uses some random build system (that was popular when they started work on the app but is now outdated) that you need to set up and learn.
Or it's a Python app that doesn't work because you don't have the right version of python and backwards compatibility is a myth.
Casual Linux things that get normal people running from the os in fear.
Package version 0.01: Built with libraries abc version 2, def version 0.1 and ghi version 7.2.2
Your system has requirements: abc version 2, def version 0.2 and ghi version 8.0.0
Package version 0.02: Requires abc version 3, def version 0.2 and ghi version 8.0.1
You realise that those differences in version would mean that you would have to basically recompile (then debug and recompile) your entire operating system with the three upgraded packages, and deal with a full cascade of dependencies, not just the package you really want to compile, OR basically sit down and rewrite Package 0.02 from the ground up using older libraries than it was originally written for.
You decide to make do with the old version of the package.
Can you not build it in a venv to not mess with your system packages?
And halfway through the compile, it fails.
"Tomorrow"