Date: Mon, 19 Aug 2013 11:16:35 +0200 From: Marcus von Appen <mva@FreeBSD.org> To: The BSD Dreamer <beastie@tardisi.com> Cc: python@freebsd.org Subject: Re: [CFT] lang/python becoming a python binary wrapper Message-ID: <20130819091635.GA1251@medusa.sysfault.org> In-Reply-To: <888dfb9c5f2e3946d8e991c23e1f2b95@lhaven.homeip.net> References: <EA3266DB-A478-45B9-B843-6BF62AF8857F@FreeBSD.org> <888dfb9c5f2e3946d8e991c23e1f2b95@lhaven.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On, Sun Aug 18, 2013, The BSD Dreamer wrote: [...] > What wasn't clear was that this applied to everybody, whether they knowingly > installed lang/python2* or lang/python3*, or not. Since, installing a port > that wants the python results in lang/python27 being installed by default > (and still does.) > > So, when I tried updating www/firefox with portmaster this morning, it broke > python for everything by updating only lang/python27 for me. What happens to > the many other fresh systems when somebody builds their first port that pulls > in the default python, which is lang/python27, but that's not enough for > satisfy the dependency? This was a serious issue in my tests, causing quite some problems and which was fixed later on that day. It should not be a problem anymore at the moment. Cheers Marcus --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlIR4nMACgkQi68/ErJnpkfUSgCeLinJgJkD+fj4OlvNhASRGbIX 9QkAnRqghOeijbwNGkxDKqOSLTOoBlpw =oi6k -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130819091635.GA1251>