Date: Wed, 26 Sep 2012 13:07:23 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Chris Rees <utisoft@gmail.com> Cc: Dmitry Sivachenko <demon@freebsd.org>, python@freebsd.org Subject: Re: bin/python3 symlink for python3X ports Message-ID: <5062C5CB.4060109@yandex.ru> In-Reply-To: <CADLo838ZysqxVHPuj6_M223ohanPWRoqc2mwePNeBYbGa2OfRQ@mail.gmail.com> References: <5062AAEA.4000401@FreeBSD.org> <CADLo838ZysqxVHPuj6_M223ohanPWRoqc2mwePNeBYbGa2OfRQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Rees wrote on 26.09.2012 13:03: > On 26 Sep 2012 08:13, "Dmitry Sivachenko" <demon@freebsd.org> wrote: >> >> Hello! >> >> It is common to have both python-2 and python-3 packages installed. >> To help transition it is convenient to have bin/python to point to > python-2 binary. >> >> Now for every X in python3X we have a bin/python3.X binary. >> >> So for every new python3.X release one should change shebang line in > scripts. >> >> I propose to tweak python3X ports so they create bin/python3 symlink > pointing to the installed python3.X binary so that people can always use > 'python3' name. >> >> What do you think? > > I think it's a great idea, at least minimising weird breakage when python > is updated. > > Have you a patch? Also, what do other OSes do? > > Chris AFAIK, linuces has python2 and python3 symlinks. So this is generally common idea. And I +1 for it. -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5062C5CB.4060109>