From owner-freebsd-ports@freebsd.org Tue Dec 5 14:08:25 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 A46AEE6AE67 for ; Tue, 5 Dec 2017 14:08:25 +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 EC2317BE2B; Tue, 5 Dec 2017 14:08:24 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id d3434e8b TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 5 Dec 2017 07:08: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: Working on FLAVOR support in portmaster From: Adam Weinberger In-Reply-To: Date: Tue, 5 Dec 2017 07:08:21 -0700 Cc: Tatsuki Makino , FreeBSD Ports ML Content-Transfer-Encoding: quoted-printable Message-Id: <1F9297F2-72E0-4AAB-938F-414A9C3E12E4@adamw.org> References: To: Stefan Esser 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: Tue, 05 Dec 2017 14:08:25 -0000 > On 5 Dec, 2017, at 0:35, Stefan Esser wrote: >=20 > Am 05.12.17 um 00:43 schrieb Tatsuki Makino: >> By the way, where is the clever way to update to flavor? >> I am using portmaster. >=20 > I'm working on FLAVOR support in portmaster. My version did already = build > all updated ports, the FLAVOR parameter is passed to build = sub-processes, > but there is still some confusion between multiple flavored versions = of the > same port (installing the py27 version wants to deinstall the py36 = version > and vice versa), which I still have to fix. >=20 > I'm not sure that I have time to complete the fix today, but it is not = too > hard. Ports need to complement the port origin with the FLAVOR, where > appropriate (e.g. when a flavored destination is found in MOVED). = Already > installed packages are annotated with "flavor" and that must be passed = to > the build command, when that port is updated. Most other logic in = portmaster > remains unaffected. >=20 >=20 > My work version has all non PKG_NG support stripped, but that is = mainly to > not waste effort fixing irrelevant sub-routines. >=20 > Is it acceptable, to have portmaster stop supporting the old package = system? > AFAIK, there is no way that a modern ports tree with flavor support = works > with a non-PKG_NG infrastructure? >=20 > Regards, STefan Thank you for doing the work!!! Yes, old package (PKG_OG?) support should be removed. Even if portmaster = supported it, the ports tree itself doesn't. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org