Date: Wed, 27 May 2009 13:35:34 -0600 From: Carl Trachte <ctrachte@gmail.com> To: python@freebsd.org Subject: Fwd: [CFT] FreeBSD python25 move to python26 as default version. Message-ID: <426ada670905271235p65ae3be9m922955fd6382181c@mail.gmail.com> In-Reply-To: <426ada670905271233t1f9ec929wab858f7a9d35d683@mail.gmail.com> References: <20090517165416.GW71804@bsdcrew.de> <4f615770905262030r71075f5bmc1bc41417d878313@mail.gmail.com> <4A1D7F2D.5010803@FreeBSD.org> <426ada670905271233t1f9ec929wab858f7a9d35d683@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, neglected to post to list. CBT ---------- Forwarded message ---------- From: Carl Trachte <ctrachte@gmail.com> Date: Wed, May 27, 2009 at 1:33 PM Subject: Re: [CFT] FreeBSD python25 move to python26 as default version. To: Doug Barton <dougb@freebsd.org> On Wed, May 27, 2009 at 11:58 AM, Doug Barton <dougb@freebsd.org> wrote: > Kelly Hays wrote: >> On Sun, May 17, 2009 at 11:54 AM, Martin Wilke <miwi@freebsd.org> wrote: >>> =A0 =A0Once the installed Python has been updated to 2.6, by using one = of the >>> =A0 =A0methods above, it is required to run the upgrade-site-packages t= arget in >>> =A0 =A0lang/python to assure that site-packages are made available to t= he new Python >>> =A0 =A0version. >>> >>> =A0 =A0# cd /usr/ports/lang/python && make upgrade-site-packages >>> >>> This Makefile target requires ports-mgmt/portupgrade to be installed. >>> >> A lot of us are no longer using ports-mgmt/portupgrade in favor of >> ports-mgmt/portmaster. Please support both tools. > > First, I don't use python, so I'm not directly affected by this. > Second, I don't think it's reasonable to _require_ that a user needs > to use any additional tools (such as portupgrade or portmaster) to do > something with the ports system. I do think it's reasonable to provide > instructions such as, "If you use toolA, do X, for toolB do Y, and if > you don't use a tool do Z, etc." > > That said, if someone can explain what it is that needs to be done, I > will be glad to help write instructions for doing it with portmaster. > > > Doug > > -- > > =A0 =A0This .signature sanitized for your protection > > _______________________________________________ > freebsd-python@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-python > To unsubscribe, send any mail to "freebsd-python-unsubscribe@freebsd.org" > I'm a pretty much a newb to BSD and have not contributed to the ports collection; apologies if I'm off track on the thread. The Python source build has IIRC an altinstall flag that allows you to have multiple versions on the machine. =A0I've got the Python from ports (I believe it's 2.5) and Python 3.0 (installed from source with altinstall) on my FreeBSD laptop. =A0I was surprised that a port for 2.6 was going to be available so soon (thanks). =A0I'm not sure if the method I've laid out for 3.0 is considered good practice within a FreeBSD context, but it's handy for having more than one version of Python on a machine. The advantage of doing the install with ports is that there is some assurance as to the security and functionality of the software (it will work under the FreeBSD OS). =A0If there is a dependence within the port, even one just required to build the port or use its Makefile, as a newb at least, I expect it to show up in the port's dependencies. My 2 cents of a possibly relevant nature. Carl T.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?426ada670905271235p65ae3be9m922955fd6382181c>