Date: Tue, 12 Dec 2017 20:34:44 +0100 From: Mathieu Arnold <mat@FreeBSD.org> To: Ben Woods <woodsb02@gmail.com>, Mathieu Arnold <mat@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r456124 - head/Mk/Uses Message-ID: <582dc2e0-9d68-c5ed-ba00-a686ee6df812@FreeBSD.org> In-Reply-To: <CAOc73CC%2B8vTnPh4A4Ea3Jdw8ut1USKk_ekkXjZXGTHKnsG7k7Q@mail.gmail.com> References: <201712121231.vBCCVBLY044497@repo.freebsd.org> <CAOc73CC%2B8vTnPh4A4Ea3Jdw8ut1USKk_ekkXjZXGTHKnsG7k7Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 12/12/2017 =C3=A0 20:17, Ben Woods a =C3=A9crit=C2=A0: > I=E2=80=99m not sure I fully understand this warning, so perhaps it nee= ds a > few more words about =E2=80=9Cwhy=E2=80=9D? Yes, this is warning is about a case that does not exist, but I was tired of arguing. > Even with flavors, it is still likely people will want 2 flavors of a > port concurrently installed. Well, if the two flavors do not conflicts, they can. > Does adding flavors already handle concurrent installation, making the > concurrent keyword unnecessary with flavors enabled? concurrent is still needed for Python ports that installs files outside of the Python lib thing. This warning is about Python ports that: - Do not use flavors - Have a USES=3Dpython defined in a way that limits it to either Python 2= *or* Python 3 - Use USE_PYTHON=3Dconcurrent There are actually no ports doing that. (Because it is stupid.) --=20 Mathieu Arnold
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?582dc2e0-9d68-c5ed-ba00-a686ee6df812>