FreeBSD 10.0-RC4 pkg upgrade QT conflict

Freddie Cash fjwcash at gmail.com
Thu Jan 16 15:59:16 UTC 2014


On Thu, Jan 16, 2014 at 5:26 AM, CeDeROM <cederom at tlen.pl> wrote:

> I have solved this issue with "pkg delete -xf qt4-; pkg upgrade" - all
> packages now match binary release, no more conflicts.
>
> I guess it was produced by compiling+installing some stuff from ports,
> which introduced some inconsistency, even though "WITH_PKGNG=yes" was set
> in /etc/make.conf...
>

​The inconsistency comes when you use a different ports tree (different
versions of things in the tree) than what was used to compile the binary
packages; or from selecting non-default OPTIONS when using the ports tree.

If you only use binary packages, there's no inconsistencies, as everything
is build at the same time, using the same ports tree and OPTIONS.

If you only use the ports tree to compile things, there's no
inconsistencies as everything is compiled (and kept up-to-date via
portmaster) using the same ports tree and OPTIONS.​

When you mix the two, inconsistencies abound.  Different ports tree lead to
different versions and/or differenet OPTIONS selected etc.

If you want to custom compile some ports, then using something like
ports-mgmt/poudriere to bulk build binary packages based on a local ports
tree is best.  That gives you the ease of upgrade/install of binary
packages, with the customisability of the ports tree, without any
inconsistencies.

​I used to be a die-hard ports tree user, customising every port and
tailoring everything to the machine.  Since pkg was released as stable,
though, I've compiled fewer and fewer ports.  My home desktop runs PC-BSD
using only binary packages, and the last 2 servers I've installed at work
have used only binary packages.  They really have come a long way ...​

-- 
Freddie Cash
fjwcash at gmail.com


More information about the freebsd-ports mailing list