From owner-freebsd-ports@freebsd.org Sun Dec 3 16:47:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C6CCDFFAEB for ; Sun, 3 Dec 2017 16:47:28 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E282D7DED9 for ; Sun, 3 Dec 2017 16:47:27 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id b536ee16 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 3 Dec 2017 09:47:22 -0700 (MST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: poudriere, python ports, and flavors oh my? From: Adam Weinberger In-Reply-To: <86lgikq6ov.fsf@newsrv.interne.associated-bears.org> Date: Sun, 3 Dec 2017 09:47:20 -0700 Cc: Christian Ullrich , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20171201175750.GA32973@vash.rhavenn.local> <57e06cb3-d4f5-3a7f-062a-619f536d8dc1@chrullrich.net> <85CBAED9-E816-461E-A409-43C4EC335BAC@adamw.org> <86lgikq6ov.fsf@newsrv.interne.associated-bears.org> To: Eric Masson X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2017 16:47:28 -0000 > On 3 Dec, 2017, at 6:31, Eric Masson wrote: >=20 > Is ports/head becoming the alter ego of src/head (possible breakages = or > disruptive new features from time to time) ? Categorically, yes, though major breakages are rare. Situations like = this, where a major new feature gets introduced and the FreeBSD = developers and community hunt down problems and solve them, is strictly = the role of HEAD. While of course we can make no *guarantees* in either = branch, ports-secteam works very hard to inspect everything that gets = merged to quarterly. > If yes, this should be written down in the handbook (chapter on ports > still states ports/head for svn retrieval) and quarterly ports = branches > should be publicized. I had no idea that the handbook was still directing people straight to = HEAD. You're absolutely right, that should be changed. Unfortunately, = directing people to an SVN path is difficult, because the SVN URL = changes every 3 months, and switching an SVN branch from one path to = another isn't completely trivial. For binary package users, new installs always default to installing = packages from quarterly, but we could do more to urge port builders = toward quarterly branches too. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org