[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#545022: (no subject)



Le Tuesday 1 February 2011 03:13:06 Leonhard Weber, vous avez écrit :
> Sorry, sounds rude, let me rephrase…
> 
> i would love to see the tools out there as a debian package. It is *the*
> thing that is missing to take PySide as the productive bindings of choice
> instead of PyQt4. Many run away in fear when they see the troublesome way
> signals are linked. Specially if they are accustomed to things I am not
> really proud of pronouncing like VisualBasic and the likes.
> 
> If there is anything y can contribute as a debian packaging layman, please
> tell me.
> 
> Thank you very much for your efforts on PySide and packaging,
> best regards,
> ~Shogun

Hi Shogun, and thanks for this rephrasing, it's much clearer and sounds better 
to my ears too.

In fact, the packaging is almost ready, and already used in PPAs for Ubuntu 
distributions, on the official PPA: https://launchpad.net/~pyside/+archive/ppa 
(unfortunately, pyside-tools tests fail to run, but that should be fixed by the 
next upstream release).

My current plan is to upload all the PySide stack (apiextractor, 
generatorrunner, shiboken, pyside, _pyside-tools_, pyside-mobility) when 
upstream tags them 1.0.0 (which should happen in some weeks now). The reason of 
the waiting is that as upstream breaks A{P,B}Is frequently during ~beta and ~rc 
releases, it's just a great amount of work to do it cleanly on Debian (where I 
can break everything on the PPAs).

Don't worry, packaging is mostly ready and will land in unstable rapidly after 
PySide 1.0.0 release.

Thanks for your understanding, cheers, 

OdyX

-- 
Didier Raboud, proud Debian Developer.
CH-1020 Renens
odyx@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: