[Pythonmac-SIG] Building packages

[konrad.hinsen at laposte.net]

On Apr 26, 2005, at 11:27, Bob Ippolito wrote:

> I do something equivalent to this (where both python installations 
> have a pth file pointing to the src directory of py2app svn trunk, and 
> the scripts dir of py2app is in my PATH):
>
> python2.4 `which bdist_mpkg` -z
> python2.3 `which bdist_mpkg` -z

Thanks, that works fine. One more technical question: how did you add 
documentation to the py2app package? By manually modifying the 
automatically generated package, or using some non-obvious 
functionality?

> ... then I move dist/*.zip to the right place, generate md5 checksums, 
> edit the data file that generates the html, run a script that makes 
> new html and then does rsync over ssh to the server.  Generally I'll 
> do my own installation by downloading from the web site and installing 
> that to make sure it works (but I only really test python 2.4 packages 
> these days).

A more strategic question: what do you see as the role of your package 
repository? A collection of what you happen to use, made public? A 
standard repository that anyone can and should contribute to? Or 
something else?

To give a concrete example, should I refer users of my packages to your 
site for stuff like NumPy, or better offer a copy on my own server to 
be sure to have 23.7 at all times?

Konrad.
--
---------------------------------------------------------------------
Konrad Hinsen
Laboratoire Léon Brillouin, CEA Saclay,
91191 Gif-sur-Yvette Cedex, France
Tel.: +33-1 69 08 79 25
Fax: +33-1 69 08 82 61
E-Mail: khinsen at cea.fr
---------------------------------------------------------------------