Date: Mon, 16 Sep 2019 23:39:29 +0900 From: Koichiro Iwao <meta@FreeBSD.org> To: Adam Weinberger <adamw@adamw.org> Cc: FreeBSD Ports <ports@freebsd.org>, ruby@freebsd.org Subject: Re: FLAVORS for Ruby Message-ID: <20190916143929.z6vnzoqjme6vw2ey@icepick.vmeta.jp> In-Reply-To: <006FCB74-04EB-4A82-A800-6C7CA273E749@adamw.org> References: <20190913074519.xfu3avb4ihmfzm2o@icepick.vmeta.jp> <CAALwa8m3NJSckxSyrVTehx3LWxheSJXxUB=iAxr%2B1HG_2WFtfg@mail.gmail.com> <20190913090645.buutinhgh2pygb4h@icepick.vmeta.jp> <CAP7rwcjH6d7AiEL4XeRyQ-evT=dq%2BZi8WDTx-aYhye-zq2DKJw@mail.gmail.com> <20190914042738.r3hedyqtpxsxnd5e@icepick.vmeta.jp> <006FCB74-04EB-4A82-A800-6C7CA273E749@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 14, 2019 at 10:52:45AM -0600, Adam Weinberger wrote: > The issue is that FLAVORS has added a substantial (and painful) complexity to python ports and python.mk. It means that a number of people have had to be hyper-vigilant and watch commits closely to catch errors introduced when people utilize the paradigm incorrectly. It’s a bitter pill, but it’s accepted because the use-case for multiple concurrent python versions is essential. > > As Antoine said, inconsistency isn’t a strong enough use case. Which brings us back to the original question: is there a specific use-case for concurrent ruby that makes the substantial increase in cognitive load, complexity, and monitoring worth it? PHP also have FLAVORS. What about PHP? Multiple concurrent PHP versions is essential? -- meta <meta@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190916143929.z6vnzoqjme6vw2ey>