this post was submitted on 06 Oct 2023
941 points (95.9% liked)
linuxmemes
21378 readers
1313 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 members of the community for any reason.
- 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.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
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. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
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 fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Isn't deb just a compressed file? Can't you just decompress it, check its dependencies and install it yourself?
What could possibly go wrong with running precompiled binaries that were linked to a set of precompiled libraries with a completely different set of precompiled libraries.
Nothing, lol. I have no issues running precompiled binaries on a fucking source-based distro.
You're not wrong, it's definitely not something a n00b should attempt in most cases. But I've done this before to save myself the need for distrobox. A lot of proprietary software only offers .deb, but is usually either statically linked or comes with its own set of nearly all the libraries it needs. So just extracting and running it often does the trick on non-debian distros like Fedora in my case.
Seriously though, just use distrobox or see if there's an unofficial package for your distro that you trust (AUR/copr/ppa/OBS). It's more straight forward especially if you don't know what you're doing.
Yup.
I don't think the libraries would be in much different places but I think it would come down to the application and imprlementation
Not the locations. The versions. Your libssl-1.0 isn't the same as mine. There often are differences in major, minor or patch versions. There even are differences in compile options where a feature present in one is not compiled in another. E.g. ciphers available in libssl.
It is. Fancy tarball.