diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101210/001689.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101210/001689.html | 134 |
1 files changed, 134 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101210/001689.html b/zarb-ml/mageia-dev/20101210/001689.html new file mode 100644 index 000000000..76fa8d3e4 --- /dev/null +++ b/zarb-ml/mageia-dev/20101210/001689.html @@ -0,0 +1,134 @@ +<!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=%3C201012101737.08275.bgmilne%40multilinks.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001688.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout&In-Reply-To=%3C201012101737.08275.bgmilne%40multilinks.com%3E" + TITLE="[Mageia-dev] Mirror layout">bgmilne at multilinks.com + </A><BR> + <I>Fri Dec 10 17:37:07 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001688.html">[Mageia-dev] Mirror layout +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1689">[ date ]</a> + <a href="thread.html#1689">[ thread ]</a> + <a href="subject.html#1689">[ subject ]</a> + <a href="author.html#1689">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Friday, 10 December 2010 16:35:09 Wolfgang Bornath wrote: +><i> 2010/12/10 Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at multilinks.com</A>>: +</I>><i> > easyurpmi should not be necessary. Users should not be expected to paste +</I>><i> > random commands from random sites into a root shell. +</I>><i> +</I>><i> Yes, if urpmi were able to switch from one mirror to another one in +</I>><i> case of any failures or at will of the user if the automatically +</I>><i> selected mirror is too slow. An issue discussed often enough since +</I>><i> Mandriva days (also reported as bug). Until this is not solved users +</I>><i> are sometimes (in germany more often than "some times") forced to use +</I>><i> such tools like easyurpmi or smarturpmi. +</I> +But, the user can also have problems here (if the mirror is too slow, if it is +behind, if it isn't maintained and users are *still* vulnerable to "rogue +mirror, keeping old vulnerable software around" issues). + +><i> > Alternatively, the whole dichotomy that necessitated contributors to +</I>><i> > create a separate project should be addressed differently, but keeping +</I>><i> > the packages integrated into the distribution, but avoiding legal issues +</I>><i> > by making it easy for entities hosting the files to avoid infringement. +</I>><i> +</I>><i> Isn't this what this whole discussion is about? There ARE legal issues +</I>><i> with some software users regard as "must have". Now, how do you avoid +</I>><i> these issues? +</I> +IMHO: +-split the software so mirrors have an easy method (e.g. rsync --exclude +'*/*/*/tainted') of avoiding software that may be risky for them to distribute +-make the mirror list api support the user submitting the repos names they +want to use (e.g. if I ask for tainted, give me a mirror for tainted, even if +'non-free' is on a different mirror) +-expose these options in the GUI, and possibly use sane defaults (possibly +even by region) +-improve automatic mirror switching in urpmi + +IMHO, media.cfg is more useful for initial (network) installation, and the +case where the user trusts their mirror. + +><i> This is the big question we have been talking about for +</I>><i> many days. +</I>><i> +</I>><i> >> Many if not all of which were in PLF for patent reasons, according to +</I>><i> >> the package description. +</I>><i> >> Which brings up a difference of PLF packages : the PLF description +</I>><i> >> usually ends with a line specifying why they are there. (At least +</I>><i> >> packages destined for Mandriva users.) +</I>><i> > +</I>><i> > Search for plf in e.g. <A HREF="http://svn.mandriva.com/cgi-">http://svn.mandriva.com/cgi-</A> +</I>><i> > bin/viewvc.cgi/packages/cooker/ffmpeg/current/SPECS/ffmpeg.spec?revision= +</I>><i> > 612098&view=markup +</I>><i> +</I>><i> Ah, does that search really give results? It should not because +</I>><i> Mandriva always stated (officially) that they have nothing to do with +</I>><i> PLF. I remember discussions where Mandriva representatives said that +</I>><i> Mandriva can not acknowledge PLF's existance. +</I> +Mandriva was subverted :-). + +Anyway, what difference does it make, whether a possible patent-infringing +feature is provided in the source, or enabled by a --with flag doesn't change +much. Unless Mandriva was going to actually remove patent infringing code in +the tarballs before committing to svn ... + +However, Mandriva packages do *NOT* in the meta-data shown to end-users +indicate anything about PLF. As such, complaints about linking to infringing +software are invalid. + +><i> BTW: there are important differences between Mandriva packages and +</I>><i> those built by PLF. Especially such as mplayer and vlc, with reasons. +</I> +Of course, but the majority are not *duplicated* from a software maintenance +perspective, that would be a waste of time. + +Regards, +Buchan +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001688.html">[Mageia-dev] Mirror layout +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1689">[ date ]</a> + <a href="thread.html#1689">[ thread ]</a> + <a href="subject.html#1689">[ subject ]</a> + <a href="author.html#1689">[ 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> |