On Thu, 18 Oct 2001, R.I.P. Deaddog wrote:
> On Thu, 18 Oct 2001, Stefan van der Eijk wrote:
>
> > >This shouldn't be difficult, using %{expand...} and %(...) .
> > >But even when kdelibs-devel is installed, one may still want to
> > >compile a bootstrapped qt2 again; perhaps it'd be better to leave
> > >the decision to those who want to compile qt2 themselves.
> > >
> > There's a "BuildConflicts: qt libqt2" in the package, which will prevent
> > kdelibs-devel (requried to build the desinger) from being installed. And
> > the package does produce qt2-designer... Weird. The BuildConflicts will
> > also need to be splitup into building designer / not building
> > designer... Why not just move the qt2-designer into a separate src.rpm
> > package?
>
> Weird... may somebody tell me why there is need to use such a BuildConflicts?
> Btw, I guess qt2-designer can not be so easily separated from qt2 main
> package... haven't tried it myself though.
Well, when I was bootstrapping QT for my computer, I needed to compile it
twice - once with all KDE references disabled, and the second time rebuilt
for KDE (after rebuilding KDE of course). I did use Mandrake SRPMS btw
A BuildConflicts is -completely- rediculous in qt2.spec. QT doesn't seem
to have any conflict with a QT that's already present... at least as near
as I can tell *g*. Oh wait - a BuildConflicts that says no qt1-devel is
appropriate. qt1/qt2 aren't compatible (for devel).
Just in my uncultured opinion mind you....
G'day, eh? :)
- Teunis
