blob: 935468982e302c83f1911fc7c6d4c263bce152b5 (
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
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Build-in or stand-alone module for X to support Y
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Build-in%20or%20stand-alone%20module%20for%20X%20to%20support%20Y&In-Reply-To=%3C4EE34CC4.4040201%40gmx.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010305.html">
<LINK REL="Next" HREF="010313.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Build-in or stand-alone module for X to support Y</H1>
<B>Kamil Rytarowski</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Build-in%20or%20stand-alone%20module%20for%20X%20to%20support%20Y&In-Reply-To=%3C4EE34CC4.4040201%40gmx.com%3E"
TITLE="[Mageia-dev] Build-in or stand-alone module for X to support Y">n54 at gmx.com
</A><BR>
<I>Sat Dec 10 13:12:52 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010305.html">[Mageia-dev] USB crash
</A></li>
<LI>Next message: <A HREF="010313.html">[Mageia-dev] Build-in or stand-alone module for X to support Y
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10311">[ date ]</a>
<a href="thread.html#10311">[ thread ]</a>
<a href="subject.html#10311">[ subject ]</a>
<a href="author.html#10311">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hello!
Situation:
A package X may have support for a package Y, by a module as a build in
X or stand-alone package. All modules are possible to turn-on and to
turn-off in a menu of X.
And there is a discussion because there is no Y at all in Mageia.
Person A says:
- include the module, even if there is no Y in Mageia (and maybe never
will be included), because an end-user can install Y from alternative
source or compile it from sources; and don't add Suggests/Requires for Y
in the package, because it's obvious that this is to support Y; also
installing Y from alternative sources/self-compilation is much simpler
than reinstalling X with support for Y
Person B says:
- don't include the module, because Y is a dependency for the module of
X - and we don't ship broken packages that aren't self-contained; so it
must be excluded from X or the nobody has package Y and maintain it
Neither A nor B want to work with Y package.
Who is right?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010305.html">[Mageia-dev] USB crash
</A></li>
<LI>Next message: <A HREF="010313.html">[Mageia-dev] Build-in or stand-alone module for X to support Y
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10311">[ date ]</a>
<a href="thread.html#10311">[ thread ]</a>
<a href="subject.html#10311">[ subject ]</a>
<a href="author.html#10311">[ 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>
|