summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-December/010319.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010319.html')
-rw-r--r--zarb-ml/mageia-dev/2011-December/010319.html154
1 files changed, 154 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010319.html b/zarb-ml/mageia-dev/2011-December/010319.html
new file mode 100644
index 000000000..3a489ab4a
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-December/010319.html
@@ -0,0 +1,154 @@
+<!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=%3C201112101448.32426.alien%40rmail.be%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="010318.html">
+ <LINK REL="Next" HREF="010322.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Build-in or stand-alone module for X to support Y</H1>
+ <B>Maarten Vanraes</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=%3C201112101448.32426.alien%40rmail.be%3E"
+ TITLE="[Mageia-dev] Build-in or stand-alone module for X to support Y">alien at rmail.be
+ </A><BR>
+ <I>Sat Dec 10 14:48:32 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="010318.html">[Mageia-dev] Build-in or stand-alone module for X to support Y
+</A></li>
+ <LI>Next message: <A HREF="010322.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#10319">[ date ]</a>
+ <a href="thread.html#10319">[ thread ]</a>
+ <a href="subject.html#10319">[ subject ]</a>
+ <a href="author.html#10319">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op zaterdag 10 december 2011 14:41:30 schreef Kamil Rytarowski:
+&gt;<i> W dniu 10.12.2011 14:11, Maarten Vanraes pisze:
+</I>&gt;<i> &gt; Op zaterdag 10 december 2011 14:06:18 schreef Kamil Rytarowski:
+</I>&gt;<i> &gt;&gt; W dniu 10.12.2011 13:45, Maarten Vanraes pisze:
+</I>&gt;<i> &gt;&gt;&gt; Op zaterdag 10 december 2011 13:12:52 schreef Kamil Rytarowski:
+</I>&gt;<i> &gt;&gt;&gt;&gt; Hello!
+</I>&gt;<i> &gt;&gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt;&gt; Situation:
+</I>&gt;<i> &gt;&gt;&gt;&gt; A package X may have support for a package Y, by a module as a build
+</I>&gt;<i> &gt;&gt;&gt;&gt; in X or stand-alone package. All modules are possible to turn-on and
+</I>&gt;<i> &gt;&gt;&gt;&gt; to turn-off in a menu of X.
+</I>&gt;<i> &gt;&gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt;&gt; And there is a discussion because there is no Y at all in Mageia.
+</I>&gt;<i> &gt;&gt;&gt;&gt; Person A says:
+</I>&gt;<i> &gt;&gt;&gt;&gt; - include the module, even if there is no Y in Mageia (and maybe never
+</I>&gt;<i> &gt;&gt;&gt;&gt; will be included), because an end-user can install Y from alternative
+</I>&gt;<i> &gt;&gt;&gt;&gt; source or compile it from sources; and don't add Suggests/Requires for
+</I>&gt;<i> &gt;&gt;&gt;&gt; Y in the package, because it's obvious that this is to support Y;
+</I>&gt;<i> &gt;&gt;&gt;&gt; also installing Y from alternative sources/self-compilation is much
+</I>&gt;<i> &gt;&gt;&gt;&gt; simpler than reinstalling X with support for Y
+</I>&gt;<i> &gt;&gt;&gt;&gt; Person B says:
+</I>&gt;<i> &gt;&gt;&gt;&gt; - don't include the module, because Y is a dependency for the module
+</I>&gt;<i> &gt;&gt;&gt;&gt; of X - and we don't ship broken packages that aren't self-contained;
+</I>&gt;<i> &gt;&gt;&gt;&gt; so it must be excluded from X or the nobody has package Y and
+</I>&gt;<i> &gt;&gt;&gt;&gt; maintain it
+</I>&gt;<i> &gt;&gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt;&gt; Neither A nor B want to work with Y package.
+</I>&gt;<i> &gt;&gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt;&gt; Who is right?
+</I>&gt;<i> &gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt; imho, if Y is wanted by some people, and X works more of less fine
+</I>&gt;<i> &gt;&gt;&gt; without Y even if it's support is compiled, and sometimes a get-Y
+</I>&gt;<i> &gt;&gt;&gt; package is fine.
+</I>&gt;<i> &gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt; imho it's maintainer's preference, if maintainer is fine to also
+</I>&gt;<i> &gt;&gt;&gt; &quot;support the Y-module for X&quot; even if depends on Y and Y is not allowed
+</I>&gt;<i> &gt;&gt;&gt; in mageia, or even if Y is in nonfree... it's fine by me.
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt; let's get into specifics:
+</I>&gt;<i> &gt;&gt; Well here there is no nonfree, demo, shareware, license issue. Just Y is
+</I>&gt;<i> &gt;&gt; yet another media-player. Importing Y is not a case for neiher A nor B.
+</I>&gt;<i> &gt;&gt; There is a question to include or not include a module (as an external
+</I>&gt;<i> &gt;&gt; package %{name}-module-mediaplayer_Y) for X. X is working perfectly
+</I>&gt;<i> &gt;&gt; without Y - Y is just adding some extra features. But the module for X
+</I>&gt;<i> &gt;&gt; is NOT working without Y. Well it's probably not breaking X, there will
+</I>&gt;<i> &gt;&gt; be an error message &quot;error loading module-mediaplayer_Y&quot;.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; you could find a way to configure it as disabled?
+</I>&gt;<i>
+</I>&gt;<i> Yes
+</I>&gt;<i>
+</I>&gt;<i> &gt; or move it to a subdir of sorts with a mention that if they do have Y
+</I>&gt;<i> &gt; that
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; they can put this file in the other dir.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; or... have a subpackage for this module and don't suggest it. plus have a
+</I>&gt;<i> &gt; warning in it to say that it requires bla.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; so my vote is for A)
+</I>&gt;<i>
+</I>&gt;<i> I like the idea with URPMI warning at the install time, this would solve
+</I>&gt;<i> the problem. &quot;If you need Y support for X, we include the module, but
+</I>&gt;<i> obtain Y at your own.&quot;
+</I>
+look at other packages, like mysql, they generate a README.install.urpmi file
+which show this text in rpmdrake
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="010318.html">[Mageia-dev] Build-in or stand-alone module for X to support Y
+</A></li>
+ <LI>Next message: <A HREF="010322.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#10319">[ date ]</a>
+ <a href="thread.html#10319">[ thread ]</a>
+ <a href="subject.html#10319">[ subject ]</a>
+ <a href="author.html#10319">[ 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>