summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016708.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-June/016708.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016708.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016708.html132
1 files changed, 132 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016708.html b/zarb-ml/mageia-dev/2012-June/016708.html
new file mode 100644
index 000000000..948ba0a4b
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016708.html
@@ -0,0 +1,132 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C72d057f73eca032c58522964ef59b36d.squirrel%40mail.rmail.be%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="016706.html">
+ <LINK REL="Next" HREF="016710.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
+ <B>AL13N</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C72d057f73eca032c58522964ef59b36d.squirrel%40mail.rmail.be%3E"
+ TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">alien at rmail.be
+ </A><BR>
+ <I>Thu Jun 21 17:27:05 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016706.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI>Next message: <A HREF="016710.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16708">[ date ]</a>
+ <a href="thread.html#16708">[ thread ]</a>
+ <a href="subject.html#16708">[ subject ]</a>
+ <a href="author.html#16708">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>&gt;<i> On 21 June 2012 14:28, AL13N &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>&gt; wrote:
+</I>&gt;&gt;&gt;<i> Well, AFAIK there is still no stance on backports policy (are we
+</I>&gt;&gt;&gt;<i> backporting from cauldron
+</I>&gt;&gt;&gt;<i> (n) to n-2 or not - if we do, we break upgradability here!).
+</I>&gt;&gt;&gt;<i> Cherry-picking backports is
+</I>&gt;&gt;&gt;<i> needed.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> This is true, but has to be solved anyway, no bearing on this problem.
+</I>&gt;&gt;<i> and
+</I>&gt;&gt;<i> cherry-picking should not be needed(since it's not supported), so that's
+</I>&gt;&gt;<i> a
+</I>&gt;&gt;<i> different problem.
+</I>&gt;<i>
+</I>&gt;<i> You claim that it's not supported.
+</I>&gt;<i> But cherry picking one backport is usually what people do.
+</I>&gt;<i>
+</I>&gt;<i> Denying the reality won't help you make progress...
+</I>
+well, this time we agreed to have supported backports.
+
+it is true that almost all devs are cherry-picking backports, but are real
+users going to do that? i doubt it, but we don't have any data about this
+in any case.
+
+the reality is that if you want supported backports, there's literally no
+way of testing if all combinations of cherrypicking will work or not.
+thus, there is no other way solution than to support only having backports
+or not.
+
+but even if you're cherry picking backports, it's still not a problem. you
+have the knowhow to cherry pick and thus also to select which ones you
+want as dependencies for updates.
+
+if everyone is cherry picking backports, there's no use to having
+supported backports, and thus we should just have unsupported backports.
+it'll make all of this alot easier.
+
+
+nonetheless, this isn't only about backports, but also for testing and 3rd
+party repos or custom repositories.
+
+in the end, the best i can come up with is to trust all enabled
+repositories. Since the user obviously trusts them.
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016706.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI>Next message: <A HREF="016710.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16708">[ date ]</a>
+ <a href="thread.html#16708">[ thread ]</a>
+ <a href="subject.html#16708">[ subject ]</a>
+ <a href="author.html#16708">[ 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>