The issue can become more complicated than one would think at first
glance. We are not yet entirely sure what sorts of conflicts exist
between qt3 and qt4, and what sort of problems might arise from having
both on a system (ie. you're compiling a program.. you now have to
explicitly tell it to use qtX, and do so, but the makefiles and config
scripts just don't want to listen. Now you're stuck with some hacks to
make, which proably won't work on the next release of the package, so
you have to do that again.)
It can get pretty messy...
-S
On Sun, Jul 03, 2005 at 01:38:50AM +0300, Vesa Kaihlavirta wrote:
> On Saturday 02 July 2005 01:59, Mircea Bardac wrote:
> > Is there a strategy for including Qt4 into ArchLinux?
>
> Nice to see you're up early :) Are there even any programs that use QT4 yet?
>
> >
> > I have the following suggestions
>
> Number two seems like the most sane choice, with a slight change.
>
> > 2.
> > a) release qt3-3.3.4-9 with "provides=(qt)"
> > b) change gradually ALL qt3 dependant apps to 'depends=("qt3")';
> > c) release qt3-3.3.4-10 with no "provides=(qt)"
> > d) check if anything breaks (if it does, return to b) )
> > e) release qt-4.0.0-1 and the apps live happily ever after
>
> I think the package name should be qt4, not just qt -- since different major
> versions of qt are not really very comparable.
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
