From owner-freebsd-current@FreeBSD.ORG Mon Jul 15 13:46:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 31318CAA for ; Mon, 15 Jul 2013 13:46:38 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id E8B57B94 for ; Mon, 15 Jul 2013 13:46:37 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Uyj6f-0001KR-Pt for freebsd-current@freebsd.org; Mon, 15 Jul 2013 15:46:25 +0200 Received: from cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com ([86.21.186.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Jul 2013 15:46:25 +0200 Received: from walterhurry by cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Jul 2013 15:46:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Walter Hurry Subject: Re: Ports with daemons on uninstall... Date: Mon, 15 Jul 2013 13:46:03 +0000 (UTC) Lines: 11 Message-ID: References: <201307141949.r6EJnZPp009319@ hergotha.csail.mit.edu> <1373895245.27518.140661255822389.195BA409@webmail. messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 13:46:38 -0000 On Mon, 15 Jul 2013 08:34:05 -0500, Mark Felder wrote: > As long as this behavior only happens during pkg installs and never with > ports, I'm OK. The worst is when a coworker forgets that the mysql port > stops the daemon and my coworker upgrades with portmaster... the daemon > is off the entire time mysql slowly compiles... I'm not familiar with portmaster, since I use portupgrade. That does the build first, then the deinstall old/install new. Seems a sensible approach anyway, in case the build fails. Doesn't portmaster work similarly?