On 12 May 1997, Ed Donovan wrote: > While the topic is raised--I installed adpkg a while ago, mistakenly > thinking it could come out cleanly if I wanted to remove it. I haven't > used deb2asc or asc2deb yet, and don't think I'm using anything else > provided by adpkg. I'd like to remove it for now, but as an 'Essential' > package dpkg/dselect doesn't want to let it go. I could > force-remove-essential it, but with it being tied so closely to dpkg, I > haven't wanted to risk that going wrong (not fully confident in my > prediction of dpkg's actions). Or I could purge it out manually. I > like to leave my dpkg and debian installation as clean and > uninterfered-with as possible, so I'm curious to hear what the group > knows before trying anything more.
if you install dpgk again before removing adpkg, nothing will break: dpkg -i dpkg_1.4.0.8.deb dpkg -r --force-remove-essential adpkg I've successfully removed adpkg from at least a dozen systems like this. I used adpkg for a while - i really like the way it's dselect scans the binary directories first and builds a list of packages to install, and i also like the way it configures packages immediately. Unfortunately, it needs some dependancy ordering so that it doesn't try configuring a package before all packages it depends on are configured - which leads to having to run Install about a million times and also manually install some packages. There are other problems with adpkg as well. adpkg shows a lot of promise, but it needs more work. craig -- craig sanders networking consultant Available for casual or contract temporary autonomous zone system administration tasks. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
