pyobjc-dev

[Pyobjc-dev] New version of package

[Bill B. <bb...@co...>]

I put a new version of the binary package on 
http://www.friday.com/software/python/

It contains the Readme and License text.   The Readme had to be edited 
to only use newlines at the end of the lines.

New package definition is in repository;   but it won't work for anyone 
but me, i bet, because of path references.

The command line 'package' tool provided by apple is totally and 
completely broken -- don't bother with it.

The whole package building process is currently manual.  It needs to be 
automated and become part of the build process.  That isn't 100% 
trivial, but at least Apple has now documented package structure a bit 
better.

b.bum

Re: [Pyobjc-dev] New version of package

[Ronald O. <ous...@ci...>]

On Sunday, Oct 13, 2002, at 17:36 Europe/Amsterdam, Bill Bumgarner 
wrote:
> The whole package building process is currently manual.  It needs to 
> be automated and become part of the build process.  That isn't 100% 
> trivial, but at least Apple has now documented package structure a bit 
> better.
It might be easier than you think. There is a script for this in the 
Python CVS repository (buildpkg.py by Dinu Gherman)

Ronald

Re: [Pyobjc-dev] New version of package

[Bill B. <bb...@co...>]

Oh, cool.  Does it support the new style packages or only old?  I'll 
have to check it out...

b.bum

On Sunday, October 13, 2002, at 12:12 PM, Ronald Oussoren wrote:

> On Sunday, Oct 13, 2002, at 17:36 Europe/Amsterdam, Bill Bumgarner 
> wrote:
>> The whole package building process is currently manual.  It needs to 
>> be automated and become part of the build process.  That isn't 100% 
>> trivial, but at least Apple has now documented package structure a 
>> bit better.
> It might be easier than you think. There is a script for this in the 
> Python CVS repository (buildpkg.py by Dinu Gherman)

[Pyobjc-dev] packaging

[<bb...@ma...>]

It only supports the old style packages -- not catastraphic, by any 
means, it'll just require a bit of work to make it generate a proper 
10.2 package.   The key advantage with 10.2 packages is that it allows 
the package to explicitly require that it be installed on the root 
volume only.

In general, the package should likely be an mpkg that contains:

     - a mandatory package containing the compiled module installed into 
/usr/lib/python2.2/site-packages

     - an optional package containing the Examples -- default 
installation into /Developer/Examples/Python/?

      -an optional package containing the Documentation (if any :-) -- 
/Developer/Documentation?

     - an optional package containing the PBX project template(s) -- 
/Developer/Project Builder Extras/....

b.bum

On Sunday, October 13, 2002, at 12:33 PM, Bill Bumgarner wrote:
[referencing the buildpkg.py script]
> Oh, cool.  Does it support the new style packages or only old?  I'll 
> have to check it out...


b.bum
Wake up. Breathe....
	.... keep breathing.