Date: Tue, 26 Sep 2017 20:30:34 -0700 From: Pete Wright <pete@nomadlogic.org> To: Mel Pilgrim <list_freebsd@bluerosetech.com>, Greg 'groggy' Lehey <grog@FreeBSD.org>, Andy Farkas <andyf@andyit.com.au> Cc: freebsd-ports@freebsd.org Subject: Re: [HEADUP] FLAVORS landing. Message-ID: <6a9e2dba-adfb-24db-9c8f-0d309e206b9e@nomadlogic.org> In-Reply-To: <60dff9c5-e64f-8069-1c41-31ecaca884df@bluerosetech.com> References: <dcc6fa75-8325-01e9-4a86-e3bc61bb27a2@FreeBSD.org> <wp4l-tjwn-wny@FreeBSD.org> <344ede5c-4147-aab3-a54e-a54aa1f6c4c5@FreeBSD.org> <59CA9EE1.7040705@andyit.com.au> <20170926235609.GC3564@eureka.lemis.com> <60dff9c5-e64f-8069-1c41-31ecaca884df@bluerosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/26/2017 17:43, Mel Pilgrim wrote: > On 09/26/2017 16:56, Greg 'groggy' Lehey wrote: >> On Wednesday, 27 September 2017 at 4:39:29 +1000, Andy Farkas wrote: >>> On 27/09/2017 04:22, Mathieu Arnold wrote: >>> >>>> Please read the whole email. >>> >>> What are FLAVORS and why do I need it? >>> >>> Is there somewhere that explains the intent and purpose? >> >> Thank you! Just the question I was going to ask. > > FLAVORS allows a pkg repo to contain variations of the same port. For > example, a port that has two mutually exclusive options can now exist > in the public repo as both builds (each with their own FLAVOR suffix), > rather than requiring the port maintainer select a default and force > users of the other to compile the port themselves, or do things like > maintain subports. thanks for the clarification - this sounds like a really useful feature for my workflow at least. i can actually think of several linux distros where something like this would have saved me lots of cycles due to having to maintain my own versions (or flavors i guess) of common packages. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a9e2dba-adfb-24db-9c8f-0d309e206b9e>