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.
I got mistaken. See replies for explanation
=======
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-getis the go to choice for modern day LinuxThere’s also the
apt-aptcommand, who triggers any audiophile to start complaining about mainstream music quality these daysI 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.
I can concur, thats what my research also indicates. Plus I am too lazy to type apt-get
Uh!? I’ve been lied to! Editing comment for clarity
Alias is your friend.
alias install=“sudo apt update && sudo apt install -y”
install git
I’d recommend avoiding aliases that conflict with regular commands, and there’s a standard Linux command called
install. https://man7.org/linux/man-pages/man1/install.1.htmlIf you’re going to always pass the -y flag then I’d add --no-install-recommends too.
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.”