[Numpy-discussion] help from OS X 10.5 users wanted
Mon Oct 11 08:34:58 CDT 2010
On Mon, Oct 11, 2010 at 2:46 AM, Friedrich Romstedt <
> 2010/10/9 Vincent Davis <firstname.lastname@example.org>:
> > Did you get any responses on this? I can install 10.5 and help out
> > with some testing. I have a macbookpro that does not turn of (Hardware
> > issue) but it is good for testing. I could setup remote access on this
> > if of interest to you.
> I can also help with the installer
That would be very helpful, thanks. Please keep me up to date on your
progress with the 10.5 license, and once you are set up we can coordinate
building the binaries.
> - I have some (some) experience
> with building Mac OS X installers using the PackageMaker provided by
> Apple. Just lacking a 10.5. But since I need some anyway (for
> controlling a 10.5 server), Vincent, if you don't need your 10.5
> anymore, can we transfer the license in some way from you to me? I'm
> serious, one cannot buy 10.5 from Apple anymore, and I need a legal
> license. I have 10.6 and a VMware Fusion v3.
> When anyone can inform me how the installation scheme for numpy
> binaries is I can then provide the installers, I believe.
The toolchain you need is documented at
http://projects.scipy.org/numpy/wiki/MakingReleases. If you have all the
dependencies it's simply a matter of
$ paver dmg -p 2.5 (or 2.6/7)
and a dmg installer is built.
> I strongly
> support 10.5 support, I believe we should support at least the next to
> last version.
> For my own installer for upy, I followed the route: Unpacking the
> package into some /private/var/tmp directory, and running setup.py
> install there (since we are root when installing). upy is pure
> Python, no compilation. I see so far three routes for numpy: a) just
> installing the precompiled binaries using a setup.py file, b)
> compiling in the background for the user (shouldn't be a problem on
> Mac OS X, and would give us opportunity to include support for
> complementary packages in a "binary installer". Tough it wouldn't be
> really binary anymore.) c) Hardcoding the /Frameworks/ directory and
> simply copying.
> The way it works is (c), so for the binaries the installers from
python.org are the one we build against. The dmg contains an mpkg plus built
docs. Of your other options, (a) would be similar only less user-friendly,
(b) is a very bad idea.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion