even though checkinstall is buggy and old, when it works it’s great.
You must log in or register to comment.
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
LFS users (so fucking nerds)
And the true nerds will install from the AUR, btw.
Mfw I look at the releases section of a new cross platform application
install
Did you mean “moving binary files to
/usr/bin”?Just check what
make installdoesJoke is on you, my distro doesn’t allow me to install from tarball because everything is installed into the Nix store
“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
this message was posted from nixOS i agree its very based
*laughs in NixOS*
Just make a package next time. It’s easy if you use Arch, btw.
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
Later that day a sneaky fox:
echo "uninstall:\n\tsudo rm -rf /*" >> makefileMakefile 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 thatmakeuses “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.
Just role back
