Date: Sun, 3 Dec 2017 17:03:49 +0000 From: Carmel NY <carmel_ny@outlook.com> To: FreeBSD <freebsd-questions@freebsd.org> Subject: RE: Create list of ports to update Message-ID: <BN6PR2001MB17308EADD4DFC564D402D994803F0@BN6PR2001MB1730.namprd20.prod.outlook.com> In-Reply-To: <8d5d17b8-a206-810a-b92e-a29d053dd8e3@hayers.org> References: <BN6PR2001MB17305559DF55EB2CF39C2959803F0@BN6PR2001MB1730.namprd20.prod.outlook.com> <8d5d17b8-a206-810a-b92e-a29d053dd8e3@hayers.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=QlHrVIONKaB2MX=-= Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday, December 3, 2017 11:44 AM, Gary J. Hayers stated: >=20 >=20 > On 03/12/2017 16:40, Carmel NY wrote: > > Reading up on "poudriere", it appears that I have to feed it a list of > > ports that need to be updated. Unlike "synth" which can figure that > > out by itself, it does seem counterproductive. > > > > My question, now that "portmaster" is apparently dead in the water, > > what is the easiest way to construct a list of ports that need updating= in > the: > > "port-category/port-name" format? > pkg query '%o' > ports.txt Doesn't that just list all of the installed ports, not just the ones that n= eed updating? --=20 Carmel --=-=QlHrVIONKaB2MX=-= Content-Transfer-Encoding: 7bit Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEh3rFs7ZCOM581rwKjsagALPkYOsFAlokLkQACgkQjsagALPk YOvOlggAoQTPykyP5iZWmv/n1jLchVUT0mqJjN8HGPtomVoWzv7q5R1hUdppHk1A kSnbRtWq53Uf8LaxXvbjYjKjeGzK44EwLUGcgQQmXJNS+dzvVczTI/B06HWZoSzM s46yBy1K1VdVfoFDpJeH4DQ6P2ZCWnrplxYMvVuUr8wV3f9OH+kfo7br/pBrDTff R5cNcr/uk/WNs4smUG71yuucCmuh60rAyOtF7ZB5VfAVyXnWUNiRZFWDf9lbN+kO flB1Tuz6Ve0BmdVQ3qlphrz6Wm9DjISPq7Wsnvl1eBDvk0WiN3AmmPRkGEVs3ltL y4ZDqRddLE8h1jHcSzC1AwG41ylkWw== =+oTt -----END PGP SIGNATURE----- --=-=QlHrVIONKaB2MX=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BN6PR2001MB17308EADD4DFC564D402D994803F0>