Re: New packages available

Tomas Pospisek's Mailing Lists <[email protected]> Tue, 20 Jan 2004 21:20:55 +0100 (CET)
Newsgroups gmane.linux.debian.kde.cvs
Message-ID <Pine.LNX.4.44.0401202118450.1019-100000@localhost>
On Tue, 20 Jan 2004, Christian Muehlhaeuser wrote:

> > > 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/.
>
> yep, true.
>
> > 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?
>
> ah, now i see. yes, you're absolutely right with this. but this has been the
> same for orth's packages, right? instead that you would have depended on
> +orth.

Yeah, that's true. But why not, as Andreas Schulz explained in his
posting, just build against Debian mainline Qt?

> actually, i'm doing it a similiar way: i'm developing with these packages on
> my machine, but for release-builiding, i'm using a clean libqt from debian on
> some other machine.
>
>
> > 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.
>
> hehe, yeah i understand. still: the only other option known to me is the one i
> just mentioned, i'm afraid.

Or build against Debian unstable?
*t

--
-----------------------------------------------------------
  Tomas Pospisek
  http://sourcepole.com -  Linux & Open Source Solutions
-----------------------------------------------------------