Date: Tue, 6 Jan 2015 18:56:49 +0100 From: Roman Naumann <roman.naumann@fu-berlin.de> To: freebsd-questions@freebsd.org Subject: Re: Questions from a Linux refugee Message-ID: <20150106175649.GB973@bulldozer.local> In-Reply-To: <20150106132934.7b2ba08c.freebsd@edvax.de> References: <20150106115503.4870ab2e@jive> <CAOc73CA9nEWSFckf2r1S9eQKWN%2Bza-NKcU_25z1EHyJDdAqPvw@mail.gmail.com> <20150106132934.7b2ba08c.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <packagename>". This might prevent upgrades, though, see "pkg help lock" for details. If you cannot upgrade any more, just use "pkg unlock <packagename>", upgrade, reinstall the package and lock it again after that. Best regards, Roman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150106175649.GB973>