Re: New packages available
Tomas Pospisek's Mailing Lists <[email protected]> Tue, 20 Jan 2004 15:47:23 +0100 (CET)
| Newsgroups | gmane.linux.debian.kde.cvs |
|---|---|
| Message-ID | <Pine.LNX.4.44.0401201538540.13899-100000@localhost> |
On Tue, 20 Jan 2004, Christian Muehlhaeuser wrote:
> > > The own QT packages would be the most important at the moment, because
> > > as the mailings about "Runaway processes" showed a
> > > all-cpu-time-consuming kded is the biggest problem at the moment.
> >
> > The problem with having your own QT Packages is that you'll exclude all
> > Debian Developpers from using your packages if they are doing anything
> > KDE/Qt related - since they won't be able to build their packages against
> > mainline qt libs...
>
> please explain to me, why this should happen? i cant see any reason, since i'm
> buildiing qt-copy.
I have not verified it, but I suppose that your KDE packages depend on
libqt from http://www.cs.uni-magdeburg.de/~aschultz/debian/unstable/.
Taken that I want to install your KDE packages [1] - that will force me to
unstall libqt from aschultz. That means if I build my package (xxdiff),
which depends on libqt, it'll depend on libqt3c102_3.2.1-6+as1, which is
not an option. Or am I misslead and there is some way around it?
Releasing a package that I don't run myself (that is: built in a chroot,
with libqt from debian-sid or testing) is not an option for me, since I
want to eat my own dogfood and be able to react to user's bugreports.
Comments?
*t
[1] which I would because konqueror from orth's build is pretty
unusable/unstable for me - crashing _a lot_ - not fun to depend on for
work.
--
-----------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
-----------------------------------------------------------