summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101211/001710.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101211/001710.html')
-rw-r--r--zarb-ml/mageia-dev/20101211/001710.html154
1 files changed, 154 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101211/001710.html b/zarb-ml/mageia-dev/20101211/001710.html
new file mode 100644
index 000000000..ad1ebf4da
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101211/001710.html
@@ -0,0 +1,154 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Mirror layout
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout&In-Reply-To=%3C4D038B30.6070004%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001707.html">
+ <LINK REL="Next" HREF="001705.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Mirror layout</H1>
+ <B>andre999</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout&In-Reply-To=%3C4D038B30.6070004%40laposte.net%3E"
+ TITLE="[Mageia-dev] Mirror layout">andr55 at laposte.net
+ </A><BR>
+ <I>Sat Dec 11 15:31:12 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001707.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI>Next message: <A HREF="001705.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1710">[ date ]</a>
+ <a href="thread.html#1710">[ thread ]</a>
+ <a href="subject.html#1710">[ subject ]</a>
+ <a href="author.html#1710">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Michael scherer a &#233;crit :
+&gt;<i>
+</I>&gt;<i> On Sat, Dec 11, 2010 at 10:52:16AM +0100, Romain d'Alverny wrote:
+</I>&gt;&gt;<i> On Sat, Dec 11, 2010 at 10:42, Michael scherer&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt; wrote:
+</I>&gt;&gt;&gt;<i> On Fri, Dec 10, 2010 at 02:26:32PM -0500, andre999 wrote:
+</I>&gt;&gt;&gt;&gt;<i> Romain d'Alverny a &#233;crit :
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i> - for packaging/shipping the distribution
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Evidently easier to package. (One less consideration.)
+</I>&gt;&gt;&gt;&gt;<i> As well, the problem doesn't exist in France, so Mageia itself won't
+</I>&gt;&gt;&gt;&gt;<i> be a target.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> This is a over simplification.
+</I>&gt;&gt;&gt;<i> PLF is not only for patented softwares, but also for softwares that
+</I>&gt;&gt;&gt;<i> have others issues ( DMCA, copyright claim, etc ).
+</I>&gt;&gt;&gt;<i> So from a packaging point of view, we would still
+</I>&gt;&gt;&gt;<i> have a separate repository, so the consideration would
+</I>&gt;&gt;&gt;<i> likely still exist.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Indeed. But it then shows that it really makes sense to separate
+</I>&gt;&gt;<i> issues per packaging media (so that end-users may decide on a
+</I>&gt;&gt;<i> case-by-case basis), provided each issue is not valid worldwide,
+</I>&gt;&gt;<i> neither uniformely.
+</I>&gt;&gt;<i>
+</I>&gt;<i> PLF has a policy ( enforced by a rpmlint module and a check at upload, iirc )
+</I>&gt;<i> of explaining why a package is in plf, and let user decide.
+</I>&gt;<i>
+</I>&gt;<i> I think that is is quite important to know why a package is in such repositories,
+</I>&gt;<i> and later, once we have a better view of what are the exact requirements of mirrors,
+</I>&gt;<i> and if this is worth, we can find a more granular system ( ie, filtering for just
+</I>&gt;<i> 2 mirrors when we will already have many others do not seem like a wise idea ).
+</I>&gt;<i>
+</I>&gt;<i> And so basically, we have 2 groups :
+</I>&gt;<i> Users and mirrors.
+</I>&gt;<i> We push the responsability to users to decide what they want to install.
+</I>&gt;<i> And for mirrors, we provide them with a simple system to decide. People
+</I>&gt;<i> who do not care do not care. People who care would likely not spend
+</I>&gt;<i> days checking every packages.
+</I>
+Sounds reasonable.
+
+As for the mirrors, I would say the best thing to do is use PLF for
+constrained packages, with their accompanying explanations.
+
+But I would be very conservative about putting patent-constrained
+software in such a repository.
+Why ? Firstly, the risk has been shown to be largely hypothetical.
+It is the companies that make a profit by selling patent-constrained
+software that are pursued.
+Besides the potential of monetory benefit from this practice, I think
+that there is another factor involved. The companies want these patents
+to be used, in order to collect royalties. They know that non-profit
+distributions will not lead to royalties. But at the same time, the
+fact that their patents are used by such distributions increases the
+prevalence of the usage, thus tends to limit the development of
+alternate technologies. The last thing they want is a viable free
+alternative to become widely available, as then profit-making royalty
+payers will have a less expensive alternative.
+So as contradictory as it may seem, it is in the interest of patent
+holders to avoid discouraging open source software from using their
+patents for free.
+
+For this reason, I would favour waiting until we (or our mirrors) are
+actually approached regarding a particular patent before considering
+removing a package from regular repositories for patent reasons.
+
+&gt;&gt;<i> Putting everything under a &quot;tainted&quot; repository will just push the
+</I>&gt;&gt;<i> problem one step aside. Putting issues separately helps having a clear
+</I>&gt;&gt;<i> policy, per type of issue (because the problem is different).
+</I>&gt;<i>
+</I>&gt;<i> Either we have 1 repository, or we have more.
+</I>
+I think that one PLF repository for constrained packages, with
+explanations of why it is there, could be a reasonable compromise.
+(Most but not all PLF packages carry an explanation.)
+Some things in PLF should definitely be excluded from Mageia, such as
+copyrighted material without permission to distribute.
+
+&gt;<i> 1 per global type of issue do not seem useful. For example, patents
+</I>&gt;<i> are per country ( or group of country ), despites some efforts to global
+</I>&gt;<i> harmonisation. The same apply to local laws ( DMCA, etc ). So saying
+</I>&gt;<i> &quot;everything patents related go there&quot; do not help much, neither mirrors or
+</I>&gt;<i> users.
+</I>
+As I explained above, I think we should not separate patent-constrained
+software until we are approached by the patenting party in question.
+This will help minimize (and maybe eliminate) the need for a set of
+constrained repositories.
+
+And have the side effect of simplifying our process, by avoiding dealing
+with the ambiguity of deciding what should be treated as
+patent-constrainted software.
+
+&gt;<i> ...
+</I>
+- Andr&#233;
+</PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001707.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI>Next message: <A HREF="001705.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1710">[ date ]</a>
+ <a href="thread.html#1710">[ thread ]</a>
+ <a href="subject.html#1710">[ subject ]</a>
+ <a href="author.html#1710">[ 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>