[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)

Fri Mar 25 14:14:49 CET 2011

On 3/25/11, Tux99 <tux99-mga at uridium.org> wrote:
+>
+>
+> Quote: yves wrote on Fri, 25 March 2011 09:42
+> ----------------------------------------------------
+>> Hi,
+>> QT4 is released since 2005, about... 6 years ?
+>> So, why is it usefull to maintain a package that "becomes" depreciated
+>> ?
+>
+> You are missing the point. QT3 is already part of Mageia and it wasn't me
+> who added it. All I'm asking is if there is any compelling reason not to
+> enable qt3-devel in the existing qt3
+> source package that is part of Mageia.
+>
+> If there isn't any COMPELLING reason, then qt3-devel should be reenabled as
+> long as someone wishes it.
+>
+
+You're missing their point.
+
+I agree, there is no 'compelling reason' not to offer it. The people
+doing the work just don't want to because enabling it means they have
+to support it. Since Mageia doesn't need it for anything, it makes no
+sense to enable it; it consumes scarce resources for no direct
+benefit. You are free to re-compile QT3 and enable it yourself, which
+is what i suggest.
+
+But I see your point as well. While Mageia may not need it, legacy
+apps may. It would seem to make no sense to deliberately break
+compatibility with legacy apps on purpose. Indeed, one of the
+strengths of Linux is the ability to support legacy apps. And since
+qt3-devel is not a stand-alone package and requires a flip of the
+switch to produce when they are compiling qt3 anyway, it seems only
+logical to go ahead and produce it too.
+
+The people who are responsible for making the final decision have
+decided not to do it, leaving you with two choices: either re-compile
+it yourself to your satisfaction or fork Mageia and make the decisions
+for the forked distro.  Again, i suggest you just re-compile QT3 for
+your personal use and make the -devel.srpm and -devel.rpm available
+for others to use.
+
+You need to move past this issue.
+
+-- 
+Hoyt
+