Date: Thu, 21 Jul 2022 09:13:45 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Tatsuki Makino <tatsuki_makino@hotmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: FLAVOR fallout? Message-ID: <Ytl7OWFQKAmrfM26@troutmask.apl.washington.edu> In-Reply-To: <PSAPR03MB5639E915C50F4E74B421A6DCFA919@PSAPR03MB5639.apcprd03.prod.outlook.com> References: <YtiR0/cPTZ%2BPp8La@troutmask.apl.washington.edu> <PSAPR03MB56393C082DB5BE5201F1913FFA919@PSAPR03MB5639.apcprd03.prod.outlook.com> <YtjZB1K/kXoLQPQh@troutmask.apl.washington.edu> <PSAPR03MB5639E915C50F4E74B421A6DCFA919@PSAPR03MB5639.apcprd03.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Not sure what the problem was. I use portmaster to manage my installed ports. Every month or two I update the OS with the buildworld dance, and then update any ports flagged by "pkg version -vl '<'". With out fail, one (or more) problem crops up, and I report it. I then find a fix for the problem and move on. To the next broken port issue. On Thu, Jul 21, 2022 at 02:57:45PM +0900, Tatsuki Makino wrote: > So is it simply because port suddenly defines FLAVOR, or is it because some port, installed by pkg-1.17.x, is uninstalled by pkg-1.18.x? > Mk/Uses/sqlite.mk was not relevant :) > > Regards. > > > Steve Kargl wrote on 2022/07/21 13:41: > > I'm in flavor of not breaking the ports system. > > Once again, removing old ports, and going into > > the spcific broken port and manual installing > > the port fixing the problem. > > -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Ytl7OWFQKAmrfM26>