On Mon, 2 Jun 2008, Graham Williams wrote:
1. Have wajig purge prompt. I often want to know whether a purge is
likely to cause problems, so I run wajig remove to see if any problems
will be caused, then wajig purge to remove the packages. This is to
avoid the situation where packages are purged but still installed
because of dependency problems, as wajig purge doesn't prompt, but just
goes ahead and tries to purge the packages you ask to be purged without
first checking dependencies.
I just use dpkg --purge here. So wajig does not dependency checks. In
fact, doesn't it fail if there are dependencies?
Yes, but the packages are still marked as "purge" afterwards, as with
(and presumably because of!) dpkg --purge.
Okay. So perhaps that's a dpkg issue? Happy to put submitted code into
wajig to address this if you have some.
I doubt that it's a dpkg issue, it seems that dpkg --purge does a simple
single thing. It's just that wajig could do something more useful. I'm not
sure how yet, but the interaction bit presumably means some programming
would be needed. If it belongs in another tool it belongs in
apt-something-or-other.
Since option 2 is also acceptable and simple to implement, I'd be happy to
see how that pans out first.
--
http://rrt.sc3d.org/ | resident, a. unable to leave (Bierce)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
