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
87
88
89
90
91
92
93
94
95
96
|
<!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%20successor%29&In-Reply-To=%3C1300918338.20983.24.camel%40akroma.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003547.html">
<LINK REL="Next" HREF="003551.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)</H1>
<B>Michael Scherer</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%20successor%29&In-Reply-To=%3C1300918338.20983.24.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)">misc at zarb.org
</A><BR>
<I>Wed Mar 23 23:12:18 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003547.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI>Next message: <A HREF="003551.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3549">[ date ]</a>
<a href="thread.html#3549">[ thread ]</a>
<a href="subject.html#3549">[ subject ]</a>
<a href="author.html#3549">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le mercredi 23 mars 2011 à 17:30 -0400, Robert Xu a écrit :
><i> On Mar 23, 2011, at 17:28, Dexter Morgan <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dmorganec at gmail.com</A>> wrote:
</I>
><i> > we will face too many pbs simple question:
</I>><i> >
</I>><i> > we provide k3b ( kde apps ) trinity provide k3b ( kde3 apps )
</I>><i>
</I>><i> Uh, no, k3b-trinity or k3b-kde3
</I>
And for configuration path, various paths in /usr/ etc ?
Library name too.
><i> >
</I>><i> > files are similar ( or named the same ), how users will distinguish
</I>><i>
</I>><i> No.. That's the purpose of /opt/kde3
</I>
/opt is in no way clean packaging. This is a violation of fhs
( <A HREF="http://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPACKAGES">http://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPACKAGES</A> ), and a rpmlint error ( dir-or-file-in-opt ).
A rpm should place stuff in /usr, unless there is a good reason.
><i> > the version it wants? how to deal with conflicts ?
</I>><i>
</I>><i> What conflicts? We're installing in a seperate prefix. Also, the RPM
</I>><i> requires, provides, conflicts, etc have long been fixed, no?
</I>
The whole conflicts/provides/requires were likely cleaned from our rpms,
and if they are not, they should be since a regular desktop
environnement should not need such provisions.
We do not had conflict between gnome and kde, or lxde and xfce, so I see
no reason to add them for kde and tde.
They were the cause of major headaches in the past, so if a package is
added, it must be clean before being uploaded.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003547.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI>Next message: <A HREF="003551.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3549">[ date ]</a>
<a href="thread.html#3549">[ thread ]</a>
<a href="subject.html#3549">[ subject ]</a>
<a href="author.html#3549">[ 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>
|
