Date: Mon, 27 Jul 2026 08:47:53 -0700 From: Steve Kargl <kargls@comcast.net> To: ports@freebsd.org Subject: Re: What is a FLAVOR and how to unbreak ports? Message-ID: <99b33d19-7ddf-4c63-bfde-6726b9656ef5@comcast.net> In-Reply-To: <20260727184705.0f0356d700c06e070edf4ae2@dec.sakura.ne.jp> References: <add809af-41f1-4f3a-9f8d-246f2a01ec36@comcast.net> <CALH631nghtQpj%2BLoxsx3SL7tfr_URbW7pHRZScLpyki8HvBjBg@mail.gmail.com> <6ce75735-75f7-4852-814c-91b8105692e6@comcast.net> <SA1PR11MB88113E9A84985B293F61293BE6CC2@SA1PR11MB8811.namprd11.prod.outlook.com> <f73caf78-c17c-40e6-9b02-c6137725029c@comcast.net> <SA1PR11MB8811F3226FA85F2D836AE4D2E6CC2@SA1PR11MB8811.namprd11.prod.outlook.com> <20260727184705.0f0356d700c06e070edf4ae2@dec.sakura.ne.jp>
index | next in thread | previous in thread | raw e-mail
On 7/27/26 02:47, Tomoaki AOKI wrote: > On Mon, 27 Jul 2026 01:25:00 -0700 > "Edward Sanford Sutton, III" <mirror176@hotmail.com> wrote: > >> On 7/26/26 19:43, Steve Kargl wrote: >>> On 7/26/26 18:41, Edward Sanford Sutton, III wrote: >>>> Flavors are a way to have separate packages created for different >>>> configurations of a port. That way users of pkg do not need to go >>>> manually build software for relatively common software variation >>>> possibilities that they may want or need in place of a single default >>>> set of options. >>> >>> Yeah, I read the porter's documentation. I could not find where >>> it mentions a comprehensive list of the FLAVORs. There is no >>> discussion of how one can query for the list of FLAVORs. >> >> Also not present in the normal handbook when talking about using the >> ports tree. Unless I'm mistaken, people shouldn't be directed to the >> porter's handbook unless trying to create or modify ports instead of >> just use them. Maybe I missed it, but I didn't find any clear definition >> of relevant variables and commands in /usr/ports/Mk files except as >> comments above sections of what is being done with blocks of code; >> normally many variables and targets are described in comments at the top >> of bsd.port.mk and if not then its in the relevant other files in there. > > I think FreeBSD project is directing regular users to pkg, > unless non-default options are needed. > And, there's the rub. Users may need/wish to drop into the ports tree to build software. On at least x86_64, the default options need to build a pkg to work on any x86_64 target. I have the following in my /etc/make.conf. FFLAGS+= -O2 -pipe -march=native -mtune=native FFLAGS+= -funroll-loops --param max-unroll-times=4 -ftree-vectorize CFLAGS+= -O2 -pipe -march=native -mtune=native -- stevehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99b33d19-7ddf-4c63-bfde-6726b9656ef5>