When removing packages it just doesn't matter. When installing, it also doesn't really matter. dpkg can't fetch packages from the repositories, but it will mark them and a following apt-get install -f will fetch them flawlessly.
A few years ago you had to be careful when mixing apt-get and aptitude, and thus probably also when mixing aptitude with dpkg, as far as i know that is not the case anymore. Even a following autoremove should work.
You haven't mentioned one single valid cause why it should be wrong to use dpkg, and I'm pretty confident that you won't, because afaik it isn't. And i'm pretty sure.
(Just jumping in because dfc mentioning he really wants to know. Just think about apt-get as a frontend for dpkg which calls dpkg to install and remove .debs, but also fetches them from the internet and notices when they are no longer needed because they were installed as a dependency for a now removed package.)
When removing packages it just doesn't matter. When installing, it also doesn't really matter. dpkg can't fetch packages from the repositories, but it will mark them and a following apt-get install -f will fetch them flawlessly.
A few years ago you had to be careful when mixing apt-get and aptitude, and thus probably also when mixing aptitude with dpkg, as far as i know that is not the case anymore. Even a following autoremove should work.
You haven't mentioned one single valid cause why it should be wrong to use dpkg, and I'm pretty confident that you won't, because afaik it isn't. And i'm pretty sure.
(Just jumping in because dfc mentioning he really wants to know. Just think about apt-get as a frontend for dpkg which calls dpkg to install and remove .debs, but also fetches them from the internet and notices when they are no longer needed because they were installed as a dependency for a now removed package.)