Date: Tue, 12 Dec 2017 09:27:29 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 224242] Some FLAVOR related changes Message-ID: <bug-224242-21822-hbmVKERPpl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224242-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-224242-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224242 --- Comment #4 from Shane <FreeBSD@ShaneWare.Biz> --- (In reply to Antoine Brodin from comment #2) > I don't think concurrent should be default, it *does* break some ports. We are trying to get python ports to build and install for multiple python versions, these concurrent breaks should get resolved as part of the update= s to support flavours. My experience with concurrent so far is that most ports o= nly need concurrent added, others need some adjustment for manpages and docs. If concurrent was enabled as a part of defining FLAVOR then USE_PYTHON=3Dnoflavors should also disable concurrent for ports it does bre= ak. Using pkg install with a port origin (or a partial name match) now finds all available flavours, without concurrent this can lead to install issues that= can frustrate users and lead to a bad user experience that will only contribute= to complaints. I reported this as a separate issue for pkg - bug #224265 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224242-21822-hbmVKERPpl>