summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101211/001707.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101211/001707.html')
-rw-r--r--zarb-ml/mageia-dev/20101211/001707.html127
1 files changed, 127 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101211/001707.html b/zarb-ml/mageia-dev/20101211/001707.html
new file mode 100644
index 000000000..8b6904b53
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101211/001707.html
@@ -0,0 +1,127 @@
+<!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=%3C20101211131633.GE14029%40sisay.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001701.html">
+ <LINK REL="Next" HREF="001710.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Mirror layout</H1>
+ <B>Michael scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout&In-Reply-To=%3C20101211131633.GE14029%40sisay.ephaone.org%3E"
+ TITLE="[Mageia-dev] Mirror layout">misc at zarb.org
+ </A><BR>
+ <I>Sat Dec 11 14:16:33 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001701.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI>Next message: <A HREF="001710.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1707">[ date ]</a>
+ <a href="thread.html#1707">[ thread ]</a>
+ <a href="subject.html#1707">[ subject ]</a>
+ <a href="author.html#1707">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Sat, Dec 11, 2010 at 10:52:16AM +0100, Romain d'Alverny wrote:
+&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;<i> &gt; On Fri, Dec 10, 2010 at 02:26:32PM -0500, andre999 wrote:
+</I>&gt;<i> &gt;&gt; Romain d'Alverny a &#233;crit :
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;&gt; &gt; &#160;- for packaging/shipping the distribution
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; Evidently easier to package. &#160;(One less consideration.)
+</I>&gt;<i> &gt;&gt; As well, the problem doesn't exist in France, so Mageia itself won't
+</I>&gt;<i> &gt;&gt; be a target.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; This is a over simplification.
+</I>&gt;<i> &gt; PLF is not only for patented softwares, but also for softwares that
+</I>&gt;<i> &gt; have others issues ( DMCA, copyright claim, etc ).
+</I>&gt;<i> &gt; So from a packaging point of view, we would still
+</I>&gt;<i> &gt; have a separate repository, so the consideration would
+</I>&gt;<i> &gt; likely still exist.
+</I>&gt;<i>
+</I>&gt;<i> Indeed. But it then shows that it really makes sense to separate
+</I>&gt;<i> issues per packaging media (so that end-users may decide on a
+</I>&gt;<i> case-by-case basis), provided each issue is not valid worldwide,
+</I>&gt;<i> neither uniformely.
+</I>&gt;<i>
+</I>PLF has a policy ( enforced by a rpmlint module and a check at upload, iirc )
+of explaining why a package is in plf, and let user decide.
+
+I think that is is quite important to know why a package is in such repositories,
+and later, once we have a better view of what are the exact requirements of mirrors,
+and if this is worth, we can find a more granular system ( ie, filtering for just
+2 mirrors when we will already have many others do not seem like a wise idea ).
+
+And so basically, we have 2 groups :
+Users and mirrors.
+We push the responsability to users to decide what they want to install.
+And for mirrors, we provide them with a simple system to decide. People
+who do not care do not care. People who care would likely not spend
+days checking every packages.
+
+&gt;<i> Putting everything under a &quot;tainted&quot; repository will just push the
+</I>&gt;<i> problem one step aside. Putting issues separately helps having a clear
+</I>&gt;<i> policy, per type of issue (because the problem is different).
+</I>
+Either we have 1 repository, or we have more.
+
+1 per global type of issue do not seem useful. For example, patents
+are per country ( or group of country ), despites some efforts to global
+harmonisation. The same apply to local laws ( DMCA, etc ). So saying
+&quot;everything patents related go there&quot; do not help much, neither mirrors or
+users.
+
+We could have one repository per country. But that would lead to
+- have a explosion of combinaison ( germany-french-non-us-non-japan-etc )
+or
+- duplicate the rpm in each country repository ( and having one
+software being forbidden in one country would requires it to be present
+on all others folder, so the growth is proportional to the number
+of country on earth ).
+
+And in both case, we would need expert from each country to decide. While
+it is already difficult for usual case, this would nearly impossible for
+everything. But not doing so would render the classification useless.
+
+So I think that the easiest way is to have 1 repository, to explain why
+packages are there, and later, once we found the ressources, to tag them,
+if there is people ready to work on it.
+
+--
+Michael Scherer
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001701.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI>Next message: <A HREF="001710.html">[Mageia-dev] Mirror layout
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1707">[ date ]</a>
+ <a href="thread.html#1707">[ thread ]</a>
+ <a href="subject.html#1707">[ subject ]</a>
+ <a href="author.html#1707">[ 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>