Date: Thu, 04 Dec 2014 22:44:14 -0800 From: Darren Pilgrim <list_freebsd@bluerosetech.com> To: "John R. Levine" <johnl@iecc.com> Cc: freebsd-questions@freebsd.org Subject: Re: switching from ports to pkg -- mailman group mismatch Message-ID: <5481543E.7040208@bluerosetech.com> In-Reply-To: <alpine.OSX.2.11.1412042255130.85870@ary.lan> References: <20141204214125.33860.qmail@ary.lan> <5480EC4B.5010803@bluerosetech.com> <alpine.OSX.2.11.1412042255130.85870@ary.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/4/2014 8:01 PM, John R. Levine wrote:
>>> 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.
This is exactly what pkg-lock solves, as you've discovered. :)
> 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.
Which port is this?
Probably the depending port has the outdated *_DEPENDS lines instead of
the appropriate *_USE varibles. Mk/bsd.database.mk is quite good at
finding percona or mariadb as a mysql dependency, but the port has to
invoke that code with a USE variable.
It's also possible the depending port is specifically asking for mysql 5.5.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5481543E.7040208>