[PyKDE] Seperate Qscintilla from PyQt

Ricardo Javier Cardenes Medina rcardenes at debian.org
Thu Dec 12 11:44:00 GMT 2002

On Wed, Dec 11, 2002 at 11:18:50PM -0800, Jim Bublitz wrote:
> My concern with splitting the packages is the possible creation of
> dependency problems for third-party developers - eg those people
> using PyQt of PyKDE to develop their packages. They should be able
> to count on a basic integral PyQt or PyKDE when distributing
> *their* packages. I'd prefer to avoid a situation similar to libc
> (hypothetically) making the socket functions optional. An app like
> eric may not have problems, but database apps (or even apps that
> peripherally use databases) will certainly expect qtsql, and apps
> that include 3D might expect qtgl. Similar dependencies might exist
> with PyKDE.

I was going to include extra information about the packages layout in
their description, but probably I should at least be consistent with the
logical layout of the other components on Debian, i.e.: if Debian's Qt
comes with SQL and OpenGL in the same package (currently, it's that way,
in the past we had a separate package for -gl), then there's no real gain
excluding them from PyQt's one.

The same comes for PyKDE, of course.

Anyway, I'm getting Qt extensions in a separate package, as even if they
come as an option at PyQt package, they depend on elements out of Qt, and
would depend and force to install extra element (QScintilla libs, in this

Thanks Jim.

More information about the PyQt mailing list