On Tuesday, March 5, 2002, at 01:29 , Alexander K. Hansen wrote:
> On 3/4/02 18:13, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > >> So I hacked a little python program to find the .deb files and >> compare them to dpkg's status file, /sw/var/lib/dpkg/status, >> and tell me which .debs are still in use. It's attached to >> this email (rather than included inline) given python's strict >> whitespace rules and most MUAs' disrespect therefor. > > I tried out the script, although I wound up having to resave it > to remove the line breaks. It worked fine for me, too. "Worked" is an interesting concept. As written, all it does is print what it might do. > One time something like this could be a problem is if you have > .debs for packages that aren't named the same, but do the same > job, like autoconf and autoconf25, or libtool and libtool14-- > some packages may require an older version of autoconf or > libtool to build correctly. However, this being said, if one > keeps the tarballs around the .deb can always be reconstituted. Fink (and my program, too) treats autoconf and autoconf25 as two separate packages. My aim was not to manage that sort of upgrade, but rather to detect and delete the leftover .debs after building a new patchlevel. For example, I'm running zlib_1.1.3-6, but I still have a boat-anchor of a .deb for zlib_1.1.3-5. I do have all the tarballs. So maybe this is a better question: What if I remove *all* of fink's .debs? That's probably a dpkg question, too. Will fink/dpkg get confused? Or, as long as I do have all the original source tarballs, are the .deb files merely time-savers should I need to re-install something? Or maybe I'll move them out of the way myself and see what happens.... Believe it or not, I actually ran Debian Linux on one of my old Macs. But I never got my head even this far around dselect/dpkg/apt until fink (slow network connection, bad user interface, little or no doc for the uninitiated). I probably have the biggest /usr/local tree of any Debian installation anywhere. > Although it _is_ a major pain to have to build emacs! :-) I've been building my own emacsen since version 18.something, so I'm used to that one. ;-) Thanks, Dan -- This email impairs your ability to operate heavy machinery. <mailto:[EMAIL PROTECTED]> _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
