Re: [Pyobjc-dev] ANN: py2app / bdist_mpkg 0.1.5 preview
Brought to you by:
ronaldoussoren
From: Joshua K. <jo...@ro...> - 2004-10-23 01:24:13
|
Bob, I just switched over to using py2app -- and it's working great! Now I=20= can toss all that XCode garbage. Joshua On Oct 20, 2004, at 9:35 PM, Bob Ippolito wrote: > I've put together a little preview of py2app 0.1.5, which has MAJOR=20 > feature enhancements over 0.1.4. > http://undefined.org/python/py2app-0.1.5.mpkg.zip (installer for = Mac=20 > OS X 10.3) > > http://svn.red-bean.com/bob/py2app/trunk (source repository) > http://svn.red-bean.com/pyobjc/branches/py2app-branch/ (PyObjC=20= > repository refactored to use py2app and bdist_mpkg) > > py2app: > non-ascii application names works now (e.g. J=E4ger) > support for non-framework builds of Python (e.g. darwinports) > slightly more documentation (INSTALLING.txt, README.txt) > PyPI information > enhanced setup.py that can use bdist_mpkg > builds and installs the py2applet tool as part of its bdist_mpkg=20= > script (to /Developer/Applications/Python Tools/py2app/) > installs the examples to /Developer/Python/py2app/Examples > > bdist_mpkg: > It's new! bdist_mpkg is a distutils command that builds a=20 > metapackage for Installer.app (or /usr/sbin/installer). It's part of=20= > the py2app suite. > It should work with ANY distutils-using Python module or = application=20 > that uses distutils and doesn't really screw up their "install"=20 > command > When using bdist_mpkg with a framework Python, it will default = the=20 > scripts installation dir to /usr/local/bin instead of the middle of=20 > nowhere inside the Python framework > It installs a script, /usr/local/bin/bdist_mpkg, which you can = use to=20 > build metapackages from any setup.py. When the metapackage is built,=20= > it will even open Installer for you (unless you pass it any --options,=20= > or just --). This is a great alternative to using python setup.py=20 > install. You can just customize and uncheck scripts, headers, etc. if=20= > you don't want to install them. > You can subclass bdist_mpkg and make it do crazy things, like = install=20 > documentation, code examples, or applications. See py2app's=20 > setup-lib/py2app_mpkg.py or PyObjC's setup-lib/pyobjc_mpkg.py (on the=20= > py2app-branch) > bdist_mpkg should become the "guts" of the next generation=20 > PackageManager instead of bdist_dumb tarballs. > will automatically determine if root permissions are required to=20= > install the package (make sure you haven't mucked with your=20 > permissions your build machine if you plan on distributing the=20 > metapackages) > > > After the dust settles a bit, probably this weekend, I'll do a more=20 > official release... but I would like to get some feedback in the=20 > meantime. > > -bob > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on=20 > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give=20= > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out=20= > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Pyobjc-dev mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyobjc-dev |