diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016712.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016712.html | 154 |
1 files changed, 154 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016712.html b/zarb-ml/mageia-dev/2012-June/016712.html new file mode 100644 index 000000000..89cfb942d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016712.html @@ -0,0 +1,154 @@ +<!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%09like%20--search-media&In-Reply-To=%3C95749392.IbOIDya8xi%40localhost%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016711.html"> + <LINK REL="Next" HREF="016716.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%09like%20--search-media&In-Reply-To=%3C95749392.IbOIDya8xi%40localhost%3E" + TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">alien at rmail.be + </A><BR> + <I>Thu Jun 21 19:33:18 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016711.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016716.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#16712">[ date ]</a> + <a href="thread.html#16712">[ thread ]</a> + <a href="subject.html#16712">[ subject ]</a> + <a href="author.html#16712">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op donderdag 21 juni 2012 17:40:51 schreef Thierry Vignaud: +><i> On 21 June 2012 17:36, AL13N <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote: +</I>><i> >> A. fetch dependencies only from enabled release/update repositories +</I>><i> >> Problems: +</I>><i> >> - patch doesn't exist yet and code complexity is alot higher +</I>><i> >> - if backports are enabled, a dependency fetched from release could +</I>><i> >> conflict with other installed (from backports or other). thus the update +</I>><i> >> would fail. +</I>><i> >> +</I>><i> >> Solutions for this: +</I>><i> >> - this is not cleanly solvable, we would have to remove the backport. +</I>><i> > +</I>><i> > [...] +</I>><i> > +</I>><i> > In this thread at the moment, I see mostly people having (personal +</I>><i> > preference) problems with how i would solve this bug. +</I>><i> > +</I>><i> > while they aren't less important, what I would rather see in this thread +</I>><i> > is alternative solutions, or how the problem with A can be solved if it +</I>><i> > happens. +</I>><i> > +</I>><i> > even if both A and B are regarded as bad, I'd even prefer people to say +</I>><i> > that B is the lesser evil. +</I>><i> > +</I>><i> > complaining on how B is not good for you, doesn't get us anywhere with +</I>><i> > this bug. +</I>><i> > +</I>><i> > So please, give alternative solutions or state how A is perfectly viable. +</I>><i> +</I>><i> You're inversing the roles :-) +</I> +inversing roles is good :-) + +><i> You cannot knowly break things just b/c of one need (which btw was +</I>><i> managed back @mdv). +</I> +well, the situations are a bit different now, we do have supported backports +now, and alot of code is now improved. + +In any case, i'd like to find out how the above problem was managed @ mdv? +perhaps since backports wasn't supported, it was also unsupported? and thus +not needing to be managed? + +><i> You're trading one infrastruture enhancement for: +</I>><i> - several new usability issues: +</I>><i> o more memory +</I>><i> o slower to compute updates +</I> +actually, it would be nice to have some data on this, according to MrsB, some +people have marked release as update media, thus alleviating their problem, +they didn't think it was a problem. + +also, when i read the code, all signs (even comments) pointed to this exact +solution (all was marked for searchmedia), and only limited on this one point. + +><i> - breaking people installation by blindly installing all backports along +</I>><i> updates if they're ever enabled. +</I> +well, as i said before, if we strictly require, it won't break. and it's not +blindly at all, only dependencies for updates marked repos. + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016711.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016716.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#16712">[ date ]</a> + <a href="thread.html#16712">[ thread ]</a> + <a href="subject.html#16712">[ subject ]</a> + <a href="author.html#16712">[ 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> |