From owner-freebsd-questions@FreeBSD.ORG Tue Jan 6 20:03:49 2015 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 67D4EBD7 for ; Tue, 6 Jan 2015 20:03:49 +0000 (UTC) Received: from mail.hemio.de (mail.hemio.de [176.9.40.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 960C28C for ; Tue, 6 Jan 2015 17:56:59 +0000 (UTC) Received: from bulldozer.local (p4FC24BC4.dip0.t-ipconnect.de [79.194.75.196]) by mail.hemio.de (Postfix) with ESMTPSA id 9DED4402 for ; Tue, 6 Jan 2015 18:56:49 +0100 (CET) Date: Tue, 6 Jan 2015 18:56:49 +0100 From: Roman Naumann To: freebsd-questions@freebsd.org Subject: Re: Questions from a Linux refugee Message-ID: <20150106175649.GB973@bulldozer.local> References: <20150106115503.4870ab2e@jive> <20150106132934.7b2ba08c.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150106132934.7b2ba08c.freebsd@edvax.de> 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: Tue, 06 Jan 2015 20:03:49 -0000 On Tue, Jan 06, 2015 at 04:32:02PM +0100, Polytropon wrote: > it's probably not that wrong to perform a command construct > like "make missing | pkg install" to get the dependencies > via pkg where possible, and then use compiling from source > where neccessary. I usually go with "make missing | pkg install -Ay" which also marks packages as automatically installed, so that "pkg autoremove" can clean them if their reverse dependency is no longer needed. > After I had it, the next update deleted it along with other > packages. How to deal with the upgrades? If it's just one or a few packages, you can lock them with "pkg lock ". This might prevent upgrades, though, see "pkg help lock" for details. If you cannot upgrade any more, just use "pkg unlock ", upgrade, reinstall the package and lock it again after that. Best regards, Roman