Updating the install_with_python.sh python version

[Michael Wood]

On 24 May 2013 16:04, Ricky Nance <ricky.nance at gmail.com> wrote:
>
> Andrew, it might not hurt to have a check, look in /tmp for the tarball,
> then use rsync (if available), if not, try wget, if not try XXX (not sure
> what solaris, freebsd, or any others have by default), if those fail, then
> error and tell the user to download the file manually to (say /tmp?) .

curl would be another one to try if you wanted to go in this
direction.  On FreeBSD (and I think other BSDs too) there is "fetch".

> Just a thought,
> Ricky
>
>
> On Thu, May 23, 2013 at 5:08 PM, Andrew Bartlett <abartlet at samba.org> wrote:
>
> > On Thu, 2013-05-23 at 09:33 -0500, Ricky Nance wrote:
> > > If you get too new of a version of python (3.0+), it can break thinks,
> > > this version is known to work with samba. I'd be willing to bet that
> > > 2.7.5 will cause things to break, but I haven't tested it myself (I
> > > want to say 2.7.3 worked, so I very well could be wrong about this).
> >
> > Actually, 2.7.5 should be fine, I would be very supprised if it isn't.
> >
> > We *do* actually need to update the version, as recent
> > Solaris/OpenIndiana versions break with the install_with_python.sh,
> > because they changed the way some network interface header worked, which
> > python compensated for in a more recent version.
> >
> > What I've just not done is tested it, then uploaded the tarball to our
> > rsync server, then update the script.  It just needs to be done, and on
> > the platforms where this is an issue, python and the development headers
> > are a native package.  (Just make sure you install the math library
> > headers, which are missing from python as a package dep...).
> >
> > Andrew Bartlett

--
Michael Wood <esiotrot at gmail.com>