Date: Sun, 3 Dec 2017 17:11:40 +0000 From: "Gary J. Hayers" <gary@hayers.org> To: FreeBSD <freebsd-questions@freebsd.org>, Carmel NY <carmel_ny@outlook.com> Subject: Re: Create list of ports to update Message-ID: <584c71d9-c97c-eb4b-66a2-b89e5cbc4daf@hayers.org> In-Reply-To: <BN6PR2001MB17308EADD4DFC564D402D994803F0@BN6PR2001MB1730.namprd20.prod.outlook.com> References: <BN6PR2001MB17305559DF55EB2CF39C2959803F0@BN6PR2001MB1730.namprd20.prod.outlook.com> <8d5d17b8-a206-810a-b92e-a29d053dd8e3@hayers.org> <BN6PR2001MB17308EADD4DFC564D402D994803F0@BN6PR2001MB1730.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/12/2017 17:03, Carmel NY wrote: > On Sunday, December 3, 2017 11:44 AM, Gary J. Hayers stated: >> >> >> 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 need updating? > It does, my apologies, I read the question wrong -- Regards, Gary J. Hayers gary@hayers.org PGP Signature https://www.hayers.org/pgp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?584c71d9-c97c-eb4b-66a2-b89e5cbc4daf>