From owner-freebsd-stable@FreeBSD.ORG Mon Nov 4 19:48:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B226903 for ; Mon, 4 Nov 2013 19:48:20 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0B4022DED for ; Mon, 4 Nov 2013 19:48:19 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C2531212F0 for ; Mon, 4 Nov 2013 14:48:18 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Mon, 04 Nov 2013 14:48:18 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=f3OEJ2LCOxo+7B8wKM0uNp80qcg=; b=FA2 MWt7a8KmMb6rVuFeu6QwRFrm2L3I648C0FqW9xL4PNfu+drJbDTI55/vTqWSxGZk WPZ7WfREOdhLkzYt3jBNkCNu1UvolEjx+2po+dLJ3igWFCF8TygbICH97XnoglSl tWy2mLSYKKwlCA9qjVbmjXVC7u6E2DGmClhQw5IQ= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id A26B410C9E1; Mon, 4 Nov 2013 14:48:18 -0500 (EST) Message-Id: <1383594498.25577.42855717.6980DEBA@webmail.messagingengine.com> X-Sasl-Enc: 9o/9bkliat/iovPfvzpVPiQEKK9Lu2SJePOScvcBUFfK 1383594498 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-d4893488 In-Reply-To: <3884C60E-FFEC-413C-901E-631E2862984B@gromit.dlib.vt.edu> References: <527406D2.7010200@intertainservices.com> <1383336649.16326.41750369.298F8E9D@webmail.messagingengine.com> <1383337118.18823.41752849.2502EBFD@webmail.messagingengine.com> <5277E53A.4090208@intertainservices.com> <3884C60E-FFEC-413C-901E-631E2862984B@gromit.dlib.vt.edu> Subject: Re: pkgng: how to upgrade a single port? Date: Mon, 04 Nov 2013 13:48:18 -0600 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 19:48:20 -0000 I now understand what you guys are trying to do, so a suggestion on how to do it: 1) Use poudriere. Make sure you have your "default" ports tree and your "production" ports tree. You can test from the default ports tree, and have a snapshot-in-time of the ports tree called "production" 2) Install/deploy your packages, do your testing, etc etc. 3) When you've finalized a "set" of packages make sure you note the exact ports tree revision and your "production" ports tree stays frozen at that revision. Do not do blind updates of this ports tree. 4) When a security or feature update happens for a package you want to upgrade, update that single port to the latest revision. Example: cd /usr/local/poudriere/ports/production/www/apache22 && svn up 5) Now you can safely build apache22, and pkg upgrade / pkg install will ONLY update that port. No other dependencies have been touched. 6) Be very paranoid and test well. Make sure you know what you're doing and be very careful that the port you updated does not have any dependencies that it expects to be updated as well. Good luck.