blob: 6327c13399fa314ce9eadcd2b6c81c0b6f237116 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qt3-devel%20needed%20for%20Trinitydesktop%20%28KDE%203.5%0A%09successor%29&In-Reply-To=%3C239f.4d8c50a7%40mageia.linuxtech.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003644.html">
<LINK REL="Next" HREF="003651.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)</H1>
<B>Tux99</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qt3-devel%20needed%20for%20Trinitydesktop%20%28KDE%203.5%0A%09successor%29&In-Reply-To=%3C239f.4d8c50a7%40mageia.linuxtech.net%3E"
TITLE="[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)">tux99-mga at uridium.org
</A><BR>
<I>Fri Mar 25 09:22:00 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003644.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI>Next message: <A HREF="003651.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3645">[ date ]</a>
<a href="thread.html#3645">[ thread ]</a>
<a href="subject.html#3645">[ subject ]</a>
<a href="author.html#3645">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
Quote: Dexter Morgan wrote on Fri, 25 March 2011 09:15
><i> > Is there any compelling reason why we cannot reenable qt3-devel in
</I>><i> > the qt3
</I>><i> > source package that is ALREADY part of Mageia?
</I>><i> >
</I>><i> > If not then I want to reenable it.
</I>><i>
</I>><i> Work on TDE on your side first, we won't reenable this old,
</I>><i> deprecated, unmaintened package is nothing really need it.
</I>><i> Reenable it locally for you, do all your work on TDE and then when you
</I>><i> will have fullfilled and pre required we will be able to start to
</I>><i> discuss about TDE.
</I>
Dexter, you didn't really answer my question, I will work on TDE by myself
but my question is about if there is any COMPELLING REASON NOT TO REENABLE
QT3-devel.
QT3 is ALREADY included in Mageia so reenabling the devel package does not
make any difference whatsoever to Mageia.
I didn't start this thread to discuss about TDE, but purely for qt3-devel.
--
Mageia ML Forum Gateway: <A HREF="http://mageia.linuxtech.net/forum/">http://mageia.linuxtech.net/forum/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003644.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI>Next message: <A HREF="003651.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3645">[ date ]</a>
<a href="thread.html#3645">[ thread ]</a>
<a href="subject.html#3645">[ subject ]</a>
<a href="author.html#3645">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
