Date: 4 Dec 2014 23:01:24 -0500 From: "John R. Levine" <johnl@iecc.com> To: freebsd-questions@freebsd.org Subject: Re: switching from ports to pkg -- mailman group mismatch Message-ID: <alpine.OSX.2.11.1412042255130.85870@ary.lan> In-Reply-To: <5480EC4B.5010803@bluerosetech.com> References: <20141204214125.33860.qmail@ary.lan> <5480EC4B.5010803@bluerosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Yes, we have a mess. If you need a port compiled with other than the >> standard options, you can't use the package, and it's a challenge >> to keep pkg from stomping your locally compiled versions. > > What issue are you seeing? One is that when pkg sees a package installed with options other than the default, it tries to reinstall the default version. Since the reason I build ports with custom options is that the default doesn't work for me, that just breaks things. The other is that when you have several ports that install approximately the same thing, such as the various forks of mysql, pkg often decides to install something that smashes an existing package. I have percona56-{server,client} installed, and every time I try pkg upgrade, it wants to install mysql55-client, which would break percona. The dependencies in the ports work, so I don't know why pkg gets it wrong. R's, John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.OSX.2.11.1412042255130.85870>