Date: Wed, 2 Jul 2014 08:41:25 +0200 From: Maciej Suszko <maciej@suszko.eu> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: Anton Sayetsky <vsjcfm@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: /usr/local/lib/compat/pkg/ cleanup ? Message-ID: <20140702084125.50882034@helium> In-Reply-To: <20140628135325.GA55592@admin.sibptus.tomsk.ru> References: <20140627161801.GA38362@admin.sibptus.tomsk.ru> <CAFG2KC%2BgC7igexqnOqgGz0s=AzMacZg=3mobvGZv97KABKOong@mail.gmail.com> <20140627165322.GA40497@admin.sibptus.tomsk.ru> <CAFG2KCLBnhXEx3B6rP6ir2hRiVvhRLiA7Lx5e_YJV2E2E2%2B1wQ@mail.gmail.com> <20140628135325.GA55592@admin.sibptus.tomsk.ru>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, 28 Jun 2014 20:53:25 +0700 Victor Sudakov <vas@mpeks.tomsk.su> wrote: > With "rm -rf /usr/local/lib/compat/pkg" you don't need all those > sophisticated tools you mentioned above. A missing library will > quickly make itself known :) and then you can forcible reinstall the > affected packages. Unless you do it remotely, using openssh from ports which might be affected... then you have a problem :) I usually do it like that: 1) find /usr/local -type f -print0 | xargs -0 ldd > /tmp/ldds 2 ) search the ldds file for "not found" or "compat" 3) find what packages affected files belongs to 4) recompile affected packages Alright, I know that in 1) the ldd command is checking much more than it has to, but running this on a system with ~1000 packages should take less than 10 minutes. -- regards, Maciej Suszko. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlOzqZUACgkQCikUk0l7iGr3xgCfX637MRWQ9jEpXBOGDfgrpQQN ZMIAnjF9b+bghxYNMbcX6EAK493sjHkS =6OYI -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140702084125.50882034>