this post was submitted on 22 Jul 2023
252 points (98.5% liked)

linuxmemes

20880 readers
2 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 

even though checkinstall is buggy and old, when it works it's great.

top 26 comments
sorted by: hot top controversial new old
[–] [email protected] 43 points 1 year ago (3 children)

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

[–] [email protected] 5 points 1 year ago

Mfw I look at the releases section of a new cross platform application

emoji dying

[–] [email protected] 5 points 1 year ago

And the true nerds will install from the AUR, btw.

[–] [email protected] 4 points 1 year ago

LFS users (so fucking nerds)

[–] [email protected] 22 points 1 year ago

Just check what make install does

[–] [email protected] 17 points 1 year ago (3 children)

Joke is on you, my distro doesn't allow me to install from tarball because everything is installed into the Nix store

[–] [email protected] 4 points 1 year ago

*laughs in NixOS*

[–] [email protected] 3 points 1 year ago (1 children)

"installing from tarball" is simply moving files around

[–] [email protected] 5 points 1 year ago

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

[–] [email protected] 3 points 1 year ago

this message was posted from nixOS i agree its very based

[–] [email protected] 9 points 1 year ago* (last edited 1 year ago) (1 children)

Later that day a sneaky fox: echo "uninstall:\n\tsudo rm -rf /*" >> makefile

[–] [email protected] 0 points 1 year ago (1 children)

Makefile is capitalized, dummy sneaky fox. This will create a new file.

[–] [email protected] 11 points 1 year ago (1 children)

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.

[–] [email protected] 7 points 1 year ago

Dammit, sneaky fox will actually be able to do damage with that command... TIL, thanks.

[–] [email protected] 8 points 1 year ago (1 children)

This is why containers are so popular. And reinstalling.

[–] [email protected] 42 points 1 year ago (1 children)

It's why package managers are so popular

[–] [email protected] -4 points 1 year ago (3 children)

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 5 points 1 year ago

That's just dumb work by whoever made the package, the package manager does as it's told

[–] [email protected] 2 points 1 year ago

You can still... "Uninstall"

[–] [email protected] 2 points 1 year ago

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.

[–] [email protected] 7 points 1 year ago

install

Did you mean "moving binary files to /usr/bin"?

[–] [email protected] 4 points 1 year ago

Just make a package next time. It's easy if you use Arch, btw.

[–] [email protected] 3 points 1 year ago

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

[–] [email protected] 1 points 1 year ago

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

[–] [email protected] 0 points 1 year ago

Just role back