On Wed, Dec 11, 2002 at 04:40:17PM -0800, Jonathan Gardner wrote: > be difficult to seperate Qscintilla into a seperate package, and PyQt's qtext > as well. While incorporating it into the PyQt package is no problem, it just > doesn't seem right. > > How does the debian package manage this?
:-? Just translate the following to the .spec equivalents. I think the only "hard" difference is that Debian dependencies rely on packages _name_, not on its content: Phil ships QScintilla as a separate package, so I packaged it _apart_ from PyQt. At Debian we split packaging information over some files into a debian/ directory, instead of a unique .spec file. There, we have a "control" file that specifies (among other things), "Build-Depends" of the package, so I can tell that I need QScintilla to build PyQt. And again, Phil doesn't make a big module with all PyQt, but has split them, and I exploit this. Into that "control" file we specify too which "binary" packages are generated from the original "source" package, so I currently ship two binary packages: python-qt3, which contains the core PyQt modules and python-qtext (which depends on python-qt3 and libqscintilla0 packages). This way, those who don't want Qt extensions, simply don't install python-qtext, but python-qt3 (or python-qt2, whatever they like). I'm even planning to split python-qt3 (which is a huge package) on several other packages, as not everyone need, say, qtgl, or qtsql. _______________________________________________ PyKDE mailing list [EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
