On Tue 03 Jun 2014 at 19:00:46 +0100, Joe wrote: > On Tue, 3 Jun 2014 12:08:13 +0300 > Andrei POPESCU <andreimpope...@gmail.com> wrote: > > > On Du, 01 iun 14, 15:36:37, Joe wrote: > > > > > > Not wishing to add confusion, but you may also find references to > > > 'dpkg'. This is the low-level package tool that all the apt tools > > > are front-ends for. It does no dependency checking, > > > > Maybe you didn't mean it this way, but dpkg does indeed do dependency > > checking. When provided with a bunch of .deb files to install it will > > take care of proper ordering when needed (Depends:, Pre-Depends:, > > etc.) and will refuse to install packages without satisfied > > dependencies unless --force switches are used. > > > > I think it's more accurate to say dpkg only handles files (be it .deb > > archives or files originating from .deb archives). It has no > > knowledge of archives, repositories, etc. > > > > Yes, what I should have written was 'doesn't automatically resolve all > dependencies', as the apt tools (mostly) do.
The advent of apt was a gigantic step forward for Debian. The interplay between dpkg and apt is still (to me) quite marvellous. Get a .deb from somewhere (Skype, for example) and dpkg -i <package> followed by apt-get -f install gets everything sorted. (I expect aptitude does the same, but I am unfamiliar with it). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/03062014191338.70255239f...@desktop.copernicus.demon.co.uk