From owner-freebsd-questions@FreeBSD.ORG Fri Dec 5 22:16:26 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8686B77C for ; Fri, 5 Dec 2014 22:16:26 +0000 (UTC) Received: from mail.parts-unknown.org (mail.parts-unknown.org [IPv6:2001:470:67:119::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 633CAEBB for ; Fri, 5 Dec 2014 22:16:26 +0000 (UTC) Received: by mail.parts-unknown.org (Postfix, from userid 1001) id 00F355F2358B; Fri, 5 Dec 2014 14:16:24 -0800 (PST) Date: Fri, 5 Dec 2014 14:16:24 -0800 From: David Benfell To: freebsd-questions@freebsd.org Subject: Re: switching from ports to pkg -- mailman group mismatch Message-ID: <20141205221624.GA41832@home.parts-unknown.org> References: <20141204164259.GA45875@home.parts-unknown.org> <20141204214125.33860.qmail@ary.lan> <20141205011041.GB11940@home.parts-unknown.org> <5482267B.8020007@bluerosetech.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <5482267B.8020007@bluerosetech.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 22:16:26 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 05, 2014 at 01:41:15PM -0800, Darren Pilgrim wrote: > On 12/4/2014 5:10 PM, David Benfell wrote: > > On Thu, Dec 04, 2014 at 09:41:25PM -0000, John Levine wrote: > >> > >> I lock the locally built packages with pkg lock, and every once in > >> a while look to see if the port's updated, in which case I unlock it > >> use portmaster to update it, then lock the new version. > > > > Is there a systematic way to tell what locked ports have been updated? >=20 > Locks don't interfere with pkg-version. >=20 So it looks like a root cron job running "pkg version -R | grep "<$" is also my friend. Thanks! --=20 David Benfell See https://parts-unknown.org/node/2 if you don't understand the attachment. --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJUgi64AAoJEBV64x4SNmAr48IQAJbhRbcZ7X//RJA1J1RZhUR9 n0oVOP+loKz1xjaJyHHtzK1E7PGt1v4p3JSPw2B5fPLi+J2FN4jF/j8myjSzUHU3 RQVmsa4kCsGdNr/WI5FQ+uDtpiJpsS2BCXqlyymVQmvbmisEGnJUoE7wNaI/Cf6/ AFUcMKTkuSJF+cy8ZANpLcP3dWs4bgxgmyucWHQUKcF3TBmYYVWb5yA2WPCv1P3/ vvWVI4E04ffeIkaj5NoiWFCW51yDxHZs+9nOm6BuRwSRKucOqGGIIifR+bh0Zu9E FDcdrbb+k/GJ7BbD+QMmV1iQ2onS6UUpYKu7vpaiR1291C6Ijo2JYwNKpJoe+GNX Yz4k1XCldZgggTL44c449sKncwpld5PndZCI0OdfxZEfhgUBUzI6w/S3AELTjeAv /kcB5cPLCwbKq8/ZCMlgM4Eafld59Z2whLRISHZrl1f9lHcgRWnPwq4ZDAGfv2ht HDp01FpENVxRsg8gNrx/R5eH/RnUYVAiTKMRTSkpXsPvC4DPcQomi/2vbXf/9dCA yzSRO+xzX/gGoGlq4/yoxTNOjF9uwCSy0m5WX4EJg340VKvYoJuaqbsL/8dBs/D2 6yDcjcoW3hDr9B+89FV/RgddACozrzMFTRMyngOOKx7YHDyb4xujAElsWttJShJY LbU2n8G2Uvfesuw7BXGx =mq6k -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd--