• Rose@slrpnk.net
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    Me, I’m old, so I just keep using apt-get, because that’s all we had back in the day, and I never bothered to learn what’s the big deal about apt. It’s just a frontend, isn’t it?

  • Matombo@feddit.org
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    apt-get has a fixed format machine parseable output

    apts output tries to be more human readable and is subject to change

  • keen@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 month ago

    Use apt in the shell and use apt-get in scripts, because apt has beautiful shell output but it isn’t script safe

    • Victor@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      Here lies dragons. Make sure you understand commands that you run on your computer. 👍

        • Rhaedas@fedia.io
          link
          fedilink
          arrow-up
          0
          ·
          1 month ago

          People don’t change. Some people look at what they’re repeating and try to understand the why, others blindly do what they are told by whom they deem as authority. LLMs are the latest, earlier were various websites (which LLMs were trained on, uh oh), still before that were the computer magazines with things to type in and the later versions even maybe a free CD of stuff. The printed media was less likely to have malicious things in them, but lord did they have errors, and the right error in the wrong place could ruin someone’s day if they just ran it without understanding it.

  • themeatbridge@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    apt is for like when you want to, and apt get is the other way to get the apt. And then if it doesn’t, sudo apt will, or then sudo apt get. Like if you’re just doing an apt, and then you also need to apt get, you can.

    • socsa@piefed.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago
      1. You can’t just be up there and just doin’ a apt like that.

      1a. An apt-get is when you

      1b. Okay well listen. An apt-get is when you get the

      1c. Let me start over

      1c-a. The user is not allowed to do a motion to the, uh, kernel, that prohibits the kernel from doing, you know, just trying to get the apt. You can’t do that.

      1c-b. Once the user is in the terminal, he can’t be over here and say to the packag, like, “I’m gonna get ya! I’m gonna apt you out! You better watch your butt!” and then just be like he didn’t even do that.

      1c-b(1). Like, if you’re about to apt and then don’t get, you have to still apt. You cannot not apt. Does that make any sense?

      1c-b(2). You gotta be, typing motion of the command, and then, until you just apt-get it.

  • RustyNova@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    Apt: get whatever is in the cached package list

    Apt-get: lookup the package to see the latest version and get that one

    Unless you always apt update, apt-get is the go to choice for modern day Linux

    There’s also the apt-apt command, who triggers any audiophile to start complaining about mainstream music quality these days

        • mutual_ayed@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          1 month ago

          Oh sorry.

          install is already a part of make/cmake as well, so it’d break any of those workflows also.

          The joke I thought I was making was “I’m too lazy to type out what I want, let’s just break the system instead.”

    • superkret@feddit.org
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      I disagree. According to Debian’s own documentation, apt is a newer front-end for your daily CLI updating and installing needs.
      It has simplified syntax, and combines the most-used functions and options.
      It is not meant for use in scripts, cause the syntax may change between versions.

      The dependency-solver in the back-end is identical.

      tl/dr:
      apt is shorter to type and will have prettier output, starting with Debian 13.
      Use apt-get inside scripts.

      • Snot Flickerman@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 month ago

        My personal experience is that apt-get will absolutely miss packages that apt will capture.

        I was actually surprised by that about six months ago and finally switched over to apt after years of apt-get.

        • superkret@feddit.org
          link
          fedilink
          arrow-up
          0
          ·
          1 month ago

          That’s actually one of the reasons I switched from Debian to Arch.
          Dependency resolution shouldn’t differ based on which front-end you use.
          Debian has dpkg, aptitude, apt-get, apt, synaptic, the Software Center…
          Fedora has rpm, dnf, yum. SUSE adds a couple more. I don’t get it.
          A linux distro should have one package manager, doing different stuff with it should be done via different commands/options inside it.

          • Rhaedas@fedia.io
            link
            fedilink
            arrow-up
            0
            ·
            1 month ago

            As a (still) Linux novice, this is something that I noticed with later distributions but never thought about your valid point. I did always wonder why there should be different places to install things in the same OS. It would probably be fine if they handled things the same, but then all you’re doing is changing the UI. It never “felt” like they did things the same.

            • superkret@feddit.org
              link
              fedilink
              arrow-up
              0
              ·
              edit-2
              1 month ago

              It can’t. I use a very simple script to combine updates and the basics of system maintenance.

              Update.sh:

              #!/usr/bin/env bash
              systemctl --failed -q
              yay -Pw
              sudo pacman -Syu
              flatpak update
              flatpak uninstall --unused
              pacman -Qqnte > ~/.local/share/applications/pkglist.txt
              pacman -Qqdtt > ~/.local/share/applications/optdeplist.txt
              pacman -Qqem > ~/.local/share/applications/foreignpkglist.txt
              pacman -Qtd
              pacman -Qm | grep -v yay-bin
              sudo find /etc -name *.pac*
              yay -Ps | grep Cache
              
  • four@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    When working with RHEL I always flip a coin to see if I’m gonna use yum or dnf this time

  • tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 month ago

    apt is newer and mostly supersedes apt-get/apt-cache/etc tools, tries to be a more-approachable frontend.

    They interoperate though, so if you’re happy with using a mix of them, go for it. I generally just use apt.

    EDIT: There were also some older attempts to produce a unified frontend, like aptitude.

    • dan@upvote.au
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      mostly supersedes apt-get/apt-cache/etc tools,

      Except for in scripts. Debian guarantee that the output format of apt-get will never change and thus it’s safe to use in scripts that parse the output, whereas they don’t have the same guarantee for apt.

    • Colloidal@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      Aptitude is great (my favorite way of managing packages), but it’s a TUI program. You can use it as CLI, at which point it mimics apt-get.

      So I would say it never attempted to unify apt commands, by rather it successfully provided a user friendly way to do most (all?) of what you could do with apt CLI tools.

  • Empricorn@feddit.nl
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    I know about these and git and flatpaks and snaps and can definitely explain them all to you! But unfortunately, I just remembered I left my oven on…