even though checkinstall is buggy and old, when it works it's great.
That's because the program developers didn't bother to put in an uninstall script
But also who installs tarballs anymore except f u c k i n g n e r d s
this post was submitted on 22 Jul 2023
257 points (98.5% liked)
linuxmemes
21180 readers
1494 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
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!
founded 1 year ago
MODERATORS
And the true nerds will install from the AUR, btw.
Mfw I look at the releases section of a new cross platform application
LFS users (so fucking nerds)
Just check what make install does
Joke is on you, my distro doesn't allow me to install from tarball because everything is installed into the Nix store
*laughs in NixOS*
this message was posted from nixOS i agree its very based
"installing from tarball" is simply moving files around
I can't let you do that, Dave - NixOS, probably
lots of folders on the system are read-only and get changed when you run rebuild
Later that day a sneaky fox: echo "uninstall:\n\tsudo rm -rf /*" >> makefile
Makefile is capitalized, dummy sneaky fox. This will create a new file.
Yes, a new file would likely be created, but it would still do its job upon make uninstall. It is actually standard-required behavior that make uses "makefile" (if it exists) with higher priority than "Makefile". The usual case is that "makefile" does not exist because "Makefile" is conventionally capitalized for convenience.
Dammit, sneaky fox will actually be able to do damage with that command... TIL, thanks.
This is why containers are so popular. And reinstalling.
It's why package managers are so popular
even package managers will still put stuff in random places like binaries outside my $PATH.. or not even clearly telling me what the binary is named or how to execute what I just installed.
That's just dumb work by whoever made the package, the package manager does as it's told
But you can do a proper uninstall. And the package manager can also give you a list of all files a package will install / installed, so you'll find stuff even in random places.
You can still... "Uninstall"
install
Did you mean "moving binary files to /usr/bin"?
Just make a package next time. It's easy if you use Arch, btw.
This is a solved problem.
grep /usr/bin/install Makefile | awk, I don't know, try fields till it looks right, then xargs rm -i and pray for the best
I just do 'locate [name of a related file]' and that's it. Pipe it into less if you can't scroll on your terminal
Just role back
view more: next ›