Date: Tue, 5 Dec 2017 08:35:55 +0100 From: Stefan Esser <se@freebsd.org> To: Tatsuki Makino <tatsuki_makino@hotmail.com>, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Working on FLAVOR support in portmaster Message-ID: <e433671c-13b1-26fa-c2e3-550b1a9e52c0@freebsd.org> In-Reply-To: <KL1PR0601MB19922BB1EBA15687D47C4CE2FA3C0@KL1PR0601MB1992.apcprd06.prod.outlook.com> References: <CAN6yY1ujLFdKpuG4Rxz%2Bfww9gAxTBaY14iCB7RFTkh-oVB1%2B9A@mail.gmail.com> <KL1PR0601MB19922BB1EBA15687D47C4CE2FA3C0@KL1PR0601MB1992.apcprd06.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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. 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. My work version has all non PKG_NG support stripped, but that is mainly to not waste effort fixing irrelevant sub-routines. 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? Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e433671c-13b1-26fa-c2e3-550b1a9e52c0>