diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016710.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016710.html | 145 |
1 files changed, 145 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016710.html b/zarb-ml/mageia-dev/2012-June/016710.html new file mode 100644 index 000000000..4dfa16edf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016710.html @@ -0,0 +1,145 @@ +<!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=%3CCAONrEtaJiNruA1HJt4ObJBBp4TgL_1mcT9Y9G%3DJym8GTca1Xtg%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016708.html"> + <LINK REL="Next" HREF="016714.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1> + <B>Thierry Vignaud</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=%3CCAONrEtaJiNruA1HJt4ObJBBp4TgL_1mcT9Y9G%3DJym8GTca1Xtg%40mail.gmail.com%3E" + TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">thierry.vignaud at gmail.com + </A><BR> + <I>Thu Jun 21 17:36:58 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016708.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016714.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#16710">[ date ]</a> + <a href="thread.html#16710">[ thread ]</a> + <a href="subject.html#16710">[ subject ]</a> + <a href="author.html#16710">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 21 June 2012 17:27, AL13N <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote: +>><i> You claim that it's not  supported. +</I>>><i> But cherry picking one backport is usually what people do. +</I>>><i> +</I>>><i> Denying the reality won't help you make progress... +</I>><i> +</I>><i> well, this time we agreed to have supported backports. +</I>><i> +</I>><i> it is true that almost all devs are cherry-picking backports, but are real +</I>><i> users going to do that? i doubt it, but we don't have any data about this +</I>><i> in any case. +</I> +End users do not know about urpmi. +They knows about mgaupdate which shows them updates and about +rpmdrake which shows everything. +Thy _ONLY_ way for them to get a backport package installed is to +manually select one. +Period. + +><i> the reality is that if you want supported backports, there's literally no +</I>><i> way of testing if all combinations of cherrypicking will work or not. +</I>><i> thus, there is no other way solution than to support only having backports +</I>><i> or not. +</I> +That's bogus. +The truth is and always has been: if you install a backport package, it's +unsupported, it's at your own risks. +Claiming we support backports would be a like: we won't retest all existing +backported packages when pushing a new one. + +><i> but even if you're cherry picking backports, it's still not a problem. you +</I>><i> have the knowhow to cherry pick and thus also to select which ones you +</I>><i> want as dependencies for updates. +</I> +You don't understand: cherry picking backports is the only way for end +users to install backports + +><i> if everyone is cherry picking backports, there's no use to having +</I>><i> supported backports, and thus we should just have unsupported backports. +</I>><i> it'll make all of this alot easier. +</I> +Indeed. As we always did. + +><i> nonetheless, this isn't only about backports, but also for testing and 3rd +</I>><i> party repos or custom repositories. +</I> +We don't support those. + +><i> in the end, the best i can come up with is to trust all enabled +</I>><i> repositories. Since the user obviously trusts them. +</I> +NACK. That's totally bogus. +Enabling the backport media DOES NOT imply "I want to install every +backports". +You're twisting the reality and the existing experience in order to match +your goals. That won't work... +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016708.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016714.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#16710">[ date ]</a> + <a href="thread.html#16710">[ thread ]</a> + <a href="subject.html#16710">[ subject ]</a> + <a href="author.html#16710">[ 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> |