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.
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.
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.
25 Comments
bdonvr@thelemmy.club · 43 pts · 3y
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
QuazarOmega@lemmy.world · 5 pts · 3y
Mfw I look at the releases section of a new cross platform application
danielton@lemmy.world · 5 pts · 3y
30p87@feddit.de · 4 pts · 3y
LFS users (so fucking nerds)
original_ish_name@latte.isnot.coffee · 23 pts · 3y
Just check what
make installdoesiopq@latte.isnot.coffee · 19 pts · 3y
Joke is on you, my distro doesn't allow me to install from tarball because everything is installed into the Nix store
nothendev@sopuli.xyz · 6 pts · 3y
*laughs in NixOS*
Steamymoomilk@sh.itjust.works · 3 pts · 3y
this message was posted from nixOS i agree its very based
InFerNo@lemmy.ml · 3 pts · 3y
"installing from tarball" is simply moving files around
iopq@latte.isnot.coffee · 5 pts · 3y
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
leo85811nardo@lemmy.world · 9 pts · 3y
Later that day a sneaky fox:
echo "uninstall:\n\tsudo rm -rf /*" >> makefileAndrew15_5@mander.xyz · 0 pts · 3y
Makefile is capitalized, dummy sneaky fox. This will create a new file.
AffineConnection@lemmy.world · 11 pts · 3y
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.Andrew15_5@mander.xyz · 7 pts · 3y
Dammit, sneaky fox will actually be able to do damage with that command... TIL, thanks.
ElectricCattleman@lemmy.world · 8 pts · 3y
This is why containers are so popular. And reinstalling.
red@feddit.de · 42 pts · 3y
It's why package managers are so popular
Ocelot@lemmies.world · -4 pts · 3y
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.
YonatanAvhar@programming.dev · 5 pts · 3y
That's just dumb work by whoever made the package, the package manager does as it's told
mexicancartel@lemmy.dbzer0.com · 2 pts · 3y
You can still... "Uninstall"
red@feddit.de · 2 pts · 3y
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.
GustavoM@lemmy.world · 7 pts · 3y
Did you mean "moving binary files to
/usr/bin"?Speiser0@feddit.de · 4 pts · 3y
Just make a package next time. It's easy if you use Arch, btw.
corsicanguppy@lemmy.ca · 3 pts · 3y
This is a solved problem.
InverseParallax@lemmy.world · 3 pts · 3y
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
EuroNutellaMan@lemmy.world · 1 pts · 3y
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
possiblylinux127@lemmy.zip · 0 pts · 3y
Just role back