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

  • bdonvr@thelemmy.club
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    3
    ·
    3 years ago

    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
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 years ago

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

    • danieltondeleted by creator
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      3 years ago

      deleted by creator

  • iopq@latte.isnot.coffee
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    1
    ·
    3 years ago

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

  • leo85811nardo
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 years ago

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

    • Andrew@mander.xyz
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      2
      ·
      3 years ago

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

      • Affine Connection
        link
        fedilink
        English
        arrow-up
        11
        ·
        3 years ago

        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.

        • Andrew@mander.xyz
          link
          fedilink
          English
          arrow-up
          7
          ·
          3 years ago

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

      • Ocelot@lemmies.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        5
        ·
        3 years ago

        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.

        • red@feddit.de
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 years 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.

  • GustavoM
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 years ago

    install

    Did you mean “moving binary files to /usr/bin”?

  • InverseParallax
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 years 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

  • EuroNutellaMan
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 years 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