Date: Wed, 16 Jan 2013 16:02:14 +0000 From: "b.f." <bf1783@googlemail.com> To: freebsd-ports@freebsd.org, Alex Stangl <alex@stangl.us> Subject: Re: Removal of Portmanager Message-ID: <CAGFTUwMAsv80GYmUrVbgvsLsm2aoh%2B6_aBJnQwsy=SSx4Bqz8A@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
>On Wed, Jan 16, 2013 at 08:48:37AM +0000, b.f. wrote: >> Mark wrote: >> >On Wed, Jan 16, 2013 at 01:51:39AM +0000, RW wrote: >> >> > Reports are sent to ports@ every 2 weeks. >> >> And I wonder how many people read carefully through all 478 entries. >> >And your suggestion is ... ? >> Try ports/ports-mgmt/portupdate-scan. > >portupdate-scan displays pertinent entries from /usr/ports/UPDATING. >How does that help you digest long lists posted on a mailing list? > Obviously, it can't: I misunderstood the original complaint. If portupdate-scan is parsing MOVED and UPDATING, it can help notify users of port removals before they update their packages, but not before the ports are removed. If users have an up-to-date ports tree in PORTSDIR, they can use something simple like: pkg_info -qoa | xargs -I @ grep -le EXPIRATION_DATE $PORTSDIR/@/Makefile to find which of their installed packages are likely to be removed, with obvious variations to list all DEPRECATED ports, etc. If they don't have a ports tree, they can use: http://portsmon.freebsd.org/portsconcordanceforexpiring.py b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGFTUwMAsv80GYmUrVbgvsLsm2aoh%2B6_aBJnQwsy=SSx4Bqz8A>