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

all 13 comments

sorted by: hot top controversial new old
[–] 5 points 3 years ago (2 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

  • source
  • hideshow 4 child comments
  • [–] 2 points 3 years ago

    install

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

  • source
  • [–] 1 point 3 years ago

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

  • source
  • [–] 1 point 3 years ago* (1 child)

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

  • source
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)

    This is why containers are so popular. And reinstalling.

  • source
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)

    It's why package managers are so popular

  • source
  • parent
  • hideshow 2 child comments