On 2010-03-03 2:19 PM, Rene Engelhard wrote: > On Wed, Mar 03, 2010 at 02:14:56PM +0100, Jürgen Strobel wrote: >> From my understanding of upstream I disagree. See > > Then you didn't read close enough. Upstream only ships a module > inside its tree. Not being in the system at all. The system integration > for that is just the proper packaging work distros do.
To be picky, upstream ships source and a default build process which builds a single (python) module inside the OOo tree. They do not prevent distro maintainers from building it multiple times with alternate configurations and storing alternate versions together with proper system integration elsewhere. Debian isn't exactly known to slavishly follow upstream build procedures everywhere. And Debian provides alternate python versions with most supplemental libraries in all versions too, it's hard to argue they are completely unsupported. As for using 2.5 everywhere myself, there are more important dependencies than OOo which mandate incompatible versions. I am using CLI+macro invocations now instead of UNO. Regards, Jürgen
signature.asc
Description: OpenPGP digital signature
