you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 1 year ago (8 children)

As someone who is confused when he has to deal with a .deb file and always has to google what to do with it - what is the advantage of a .deb over let's say a shell script?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 13 points 1 year ago* (last edited 1 year ago) (3 children)

    I never fully trust a shell script and usually end up reading any I have to use first, so I know what they do. And after so many years dpkg holds no mysteries for me and Discover will install .debs if I double click while in KDE.

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

    It's worth knowing that .deb files can contain setup scripts that get run as root when installed, so you should trust them too.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 year ago* (last edited 1 year ago) (1 child)

    Yeah. They all come with risks, but I psychologically struggle to run shell scripts unless I know what's in them. And the same brain dysfunction makes my automatically distrust a script that doesn't set pipefail.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 10 points 1 year ago

    If made correctly (which is hilariously easy), it's a clean install and uninstall process, support some level of potential conflict regarding files that are shared with other packages/commands, support dependencies out of the box, and with minimal work can be made easy to update for the user (even automatically updates, depending on the user's choices) by having an (again, very easy to setup for a dev) repository. With the added value of authenticity checks before updating.

    All this in a standardized way that requires no tinkering, compatibility stuff, etc, because all these checks are built-in.

    Note that some of this probably applies to other system package management solutions, it's not exclusive to .deb.

  • source
  • parent
  • [–] 7 points 1 year ago*

    dpkg -i <nameofpackage.deb>

    Which can be read as: (Debpackage) -install <nameofpackage.deb>

    That's it!

    Also, if you haven't already, install tldr (apt install tldr), then you can 'tldr deb' (or any other command) to get a few examples of their most used functions.

  • source
  • parent