apt and apt-get both use dpkg internally, but these days it’s essentially seen as an implementation detail that regular users don’t née to know about.
dpkg doesn’t resolve dependencies (that’s a feature of apt) which means that if you install a Debian package with dpkg, you’ll have to manually install all dependencies first, and they won’t be marked as automatically installed (so autoremove won’t remove them if they’re not needed any more). Using apt solves that.
The web suggests dpkg because either the articles are old, or they’re based on outdated knowledge :)
dpkg doesn’t resolve dependencies (that’s a feature of apt) which means that if you install a Debian package with dpkg, you’ll have to manually install all dependencies first, and they won’t be marked as automatically installed
Usually installing a manually downloaded package and its dependencies works like this: # dpkg -i package-file.deb # apt-get -f install
So apt-get can be used to install missing dependencies afterwards while marking them as automatically installed.
apt and apt-get both use dpkg internally, but these days it’s essentially seen as an implementation detail that regular users don’t née to know about.
dpkg doesn’t resolve dependencies (that’s a feature of apt) which means that if you install a Debian package with dpkg, you’ll have to manually install all dependencies first, and they won’t be marked as automatically installed (so autoremove won’t remove them if they’re not needed any more). Using apt solves that.
The web suggests dpkg because either the articles are old, or they’re based on outdated knowledge :)
@[email protected]
Usually installing a manually downloaded package and its dependencies works like this:
# dpkg -i package-file.deb# apt-get -f installSo apt-get can be used to install missing dependencies afterwards while marking them as automatically installed.
That works, but why do that when you could just do
apt install ./package-file.deb?