Hi, Hopefully to help clarify a few things ...
Please see: http://www.budischewski.com/pyuno/python-bridge.html So yes there is a forthcoming pyuno module from upstream and even a forthcoming python module (since if you use two different gcc 3 versions to compile the bridge and python there is a problem). Both of these pieces work well right now in OO643C and later and could esily be added to anyone release build if they wanted to add it. You literally unpack both tarballs into the >= 643C tree and build just like any other module. I assume there will be scp changes to install it via the installer but since you use your own packages, that shouldn't even matter. Hope this helps, Kevin On February 26, 2003 08:36 am, Chris Halls wrote: > On Wed, Feb 26, 2003 at 11:53:43AM +0100, Jerome Warnier wrote: > > >What exactly do you need from the packages? If you say what you are using > > >I'll try and consider it when prioritising the split. > > It would probably be usefull to try to package PyUNO to a Debian package. > > I think that current PyUNO would hardly work on <1.1, though. > > I meant what is needed from the upstream source. PyUNO is not part of that. > > Chris > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
