Date: Fri, 2 Mar 2018 00:32:24 -0800 From: Yuri <yuri@freebsd.org> To: koobs@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, python <python@freebsd.org> Cc: "Tobias C. Berner" <tcberner@freebsd.org> Subject: Re: svn commit: r463374 - head/security/nyx Message-ID: <848460b9-1e0b-2a36-abc8-bfa130dee349@freebsd.org> In-Reply-To: <531069af-c0fc-1b2c-0c91-52cd73ba001e@FreeBSD.org> References: <201803020651.w226ptn3091275@repo.freebsd.org> <6f698e1f-a5d5-2cd7-b2b7-c288a3c65bb6@FreeBSD.org> <6dd4b973-fbcb-8fa8-fb3e-1cece416898f@freebsd.org> <531069af-c0fc-1b2c-0c91-52cd73ba001e@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/01/18 23:57, Kubilay Kocak wrote: > 1) Assuming what users care about is risky business. Port has to provide to users functionality that they expect. If port is an app, executable provides this functionality. Executables based on different python versions are expected to work the same way. If they don't work the same way, this is a bug. Packages aren't created in order to allow users to detect bugs, or to compare performance, therefore there should be no need to build multiple packages for apps. If some expert user will want to test with some other python versions, he still can do this by rebuilding it locally. This was the logic why I added noflavors. For libraries though functionality is a set of python modules, therefore they should be in all flavors. What you suggest (to have flavors for apps) just doesn't seem to have any benefit. :) Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?848460b9-1e0b-2a36-abc8-bfa130dee349>