pyobjc-dev

[Pyobjc-dev] Where is pkg?

[Rich H. <ric...@ga...>]

I'm a few years away from my last use of any version control
stuff, but I just don't find any Pyobjc-1.4 package file
or anything like it.  I also find a few broken links around
sourceforge.  I need to install the above package on my
MacBook running 10.4.11, to use some software that depends
on it.

Where is it?  I found 1.3.7 hanging around at sourceforge,
and I looked through the subversion server and found a tree for
1.4, even a subtree targeted for 10.4, but no software to
download.  Even a few dependencies for it.

The archives for this list aren't working, either.

Any tips?

rich
--
\  Rich Hammett       http://home.hiwaay.net/~rhammett
/  ric...@ga...   Against the run-of-the-mill
\                               --static as it seems--
/                            we break the surface tension
\                            with our wild kinetic dreams.

Re: [Pyobjc-dev] Where is pkg?

[David B. <db3...@gm...>]

Rich Hammett <ric...@ga...> writes:

> Where is it?  I found 1.3.7 hanging around at sourceforge,
> and I looked through the subversion server and found a tree for
> 1.4, even a subtree targeted for 10.4, but no software to
> download.  Even a few dependencies for it.

I believe the older pyobjc-1.4 download was just a tar image from the
source tree.  The current download page:

    http://pyobjc.sourceforge.net/downloads.html

has a pointer to the 1.4 source branch at:

    http://svn.red-bean.com/pyobjc/branches/pyobjc-1.4-branch

So, if you want 1.4, just grab a copy of that branch, and then use the
setup.py to build it.  Grabbing a copy is probably simplest with a
command line svn tool via:

    svn export http://svn.red-bean.com/pyobjc/branches/pyobjc-1.4-branch

which will give you the tree in a pyobjc-1.4-branch directory beneath
where you run the command.

Note when I built it a while back, I modified setup.py to set
AUTO_UNIVERSAL to 1 to generate a universal binary version.  If you're
just building on and targeting newer Intel Macs, probably no need to
do that.

I believe you can install directly from setup, but I used bdist_mpkg
to generate an OSX-compatible installer package first and then
installed that.

-- David