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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
|
<!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=%3C4EE3618A.4030105%40gmx.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010316.html">
<LINK REL="Next" HREF="010319.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=%3C4EE3618A.4030105%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 14:41:30 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010316.html">[Mageia-dev] Build-in or stand-alone module for X to support Y
</A></li>
<LI>Next message: <A HREF="010319.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#10318">[ date ]</a>
<a href="thread.html#10318">[ thread ]</a>
<a href="subject.html#10318">[ subject ]</a>
<a href="author.html#10318">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>W dniu 10.12.2011 14:11, Maarten Vanraes pisze:
><i> Op zaterdag 10 december 2011 14:06:18 schreef Kamil Rytarowski:
</I>>><i> W dniu 10.12.2011 13:45, Maarten Vanraes pisze:
</I>>>><i> Op zaterdag 10 december 2011 13:12:52 schreef Kamil Rytarowski:
</I>>>>><i> Hello!
</I>>>>><i>
</I>>>>><i> Situation:
</I>>>>><i> A package X may have support for a package Y, by a module as a build in
</I>>>>><i> X or stand-alone package. All modules are possible to turn-on and to
</I>>>>><i> turn-off in a menu of X.
</I>>>>><i>
</I>>>>><i> And there is a discussion because there is no Y at all in Mageia.
</I>>>>><i> Person A says:
</I>>>>><i> - include the module, even if there is no Y in Mageia (and maybe never
</I>>>>><i> will be included), because an end-user can install Y from alternative
</I>>>>><i> source or compile it from sources; and don't add Suggests/Requires for Y
</I>>>>><i> in the package, because it's obvious that this is to support Y; also
</I>>>>><i> installing Y from alternative sources/self-compilation is much simpler
</I>>>>><i> than reinstalling X with support for Y
</I>>>>><i> Person B says:
</I>>>>><i> - don't include the module, because Y is a dependency for the module of
</I>>>>><i> X - and we don't ship broken packages that aren't self-contained; so it
</I>>>>><i> must be excluded from X or the nobody has package Y and maintain it
</I>>>>><i>
</I>>>>><i> Neither A nor B want to work with Y package.
</I>>>>><i>
</I>>>>><i> Who is right?
</I>>>><i> imho, if Y is wanted by some people, and X works more of less fine
</I>>>><i> without Y even if it's support is compiled, and sometimes a get-Y
</I>>>><i> package is fine.
</I>>>><i>
</I>>>><i> imho it's maintainer's preference, if maintainer is fine to also "support
</I>>>><i> the Y-module for X" even if depends on Y and Y is not allowed in mageia,
</I>>>><i> or even if Y is in nonfree... it's fine by me.
</I>>>><i> let's get into specifics:
</I>>><i> Well here there is no nonfree, demo, shareware, license issue. Just Y is
</I>>><i> yet another media-player. Importing Y is not a case for neiher A nor B.
</I>>><i> There is a question to include or not include a module (as an external
</I>>><i> package %{name}-module-mediaplayer_Y) for X. X is working perfectly
</I>>><i> without Y - Y is just adding some extra features. But the module for X
</I>>><i> is NOT working without Y. Well it's probably not breaking X, there will
</I>>><i> be an error message "error loading module-mediaplayer_Y".
</I>><i> you could find a way to configure it as disabled?
</I>Yes
><i> or move it to a subdir of sorts with a mention that if they do have Y that
</I>><i> they can put this file in the other dir.
</I>><i>
</I>><i> or... have a subpackage for this module and don't suggest it. plus have a
</I>><i> warning in it to say that it requires bla.
</I>><i>
</I>><i> so my vote is for A)
</I>I like the idea with URPMI warning at the install time, this would solve
the problem. "If you need Y support for X, we include the module, but
obtain Y at your own."
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010316.html">[Mageia-dev] Build-in or stand-alone module for X to support Y
</A></li>
<LI>Next message: <A HREF="010319.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#10318">[ date ]</a>
<a href="thread.html#10318">[ thread ]</a>
<a href="subject.html#10318">[ subject ]</a>
<a href="author.html#10318">[ 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>
|
