Working on FLAVOR support in portmaster

Rainer Hurling rhurlin at gwdg.de
Tue Dec 5 19:23:55 UTC 2017


Am 05.12.2017 um 08:35 schrieb Stefan Esser:
> 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.

Isn't the described behaviour (installing the py27 version wants to
deinstall the py36 version and vice versa) caused by the underlying
ports mechanisms? As far as I can see, portmaster gives exactly the
output, that also comes from using pure 'make deinstall' and 'make
reinstall'.

> 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

Many thanks for your efforts in bringing flavors into portmaster. Really
appreciated!

Regards,
Rainer


More information about the freebsd-ports mailing list