On Sat, 6 Feb 1999 09:50:37 -0800 (PST), rrr <[EMAIL PROTECTED]> said: > I can't let this slide. ;) I do know what I'm doing (been using > Linux 4 or 5 years) - what I'm not entirely up to speed on is > Debian's package management system.
Oh, I really didn't mean to impinge your skill or knowledge. > The fact is, is that by (foolishly) removing libncurses my ability > to repair the damage was non-existant (no installed ftp clients will > work without libncurses). I then foolishly used the recovery floppy > - this is what trashed my dpkg status files i.e. it overwrote them > with hamm stuff and assumed a new install. My biggest mistake was > becoming so dependant on this menu driven tool in the first place. > I started using Debian because I wanted something that would keep > track of obsolete libs and dependancies across software upgrades. > As dpkg can't even tell what is (it sees the important stuff - but > not a lot of other packages that are installed) installed at this > point and that there is no way to rebuild that information short of > a full reinstall - I'm wondering "what did I gain by switching from > Slackware?" Well, I understand that, but, you know, the dpkg status file *is* where this information is stored. > I am going to write a script that will parse the install scripts and > tell me if _every_ file that a particular package installs is > installed. If so I will check it by hand. If it is indeed > installed, I'll change the status file hand. This seems easier than > a full re-install and will at least give the peace of mind that dpkg > has a clue as to what's on the system. Yeah, so long as you get all the versions right. > Guess I didn't learn that lesson, eh? I don't learn when things > work right anyway - I learn by breaking then fixing stuff. <rofl> Yeah, me too. -- .....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
