diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010440.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010440.html | 123 |
1 files changed, 123 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010440.html b/zarb-ml/mageia-dev/2011-December/010440.html new file mode 100644 index 000000000..a5f531792 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010440.html @@ -0,0 +1,123 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How broken are RPM dependencies allowed to be? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3CCA%2BCX%2Bbii%3DT6gQOY6hXpgzHAFrj41WwGuWtmLQoaNqpxmnj1_xA%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="010429.html"> + <LINK REL="Next" HREF="010419.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How broken are RPM dependencies allowed to be?</H1> + <B>Pascal Terjan</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3CCA%2BCX%2Bbii%3DT6gQOY6hXpgzHAFrj41WwGuWtmLQoaNqpxmnj1_xA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] How broken are RPM dependencies allowed to be?">pterjan at gmail.com + </A><BR> + <I>Wed Dec 14 22:44:09 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010429.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI>Next message: <A HREF="010419.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10440">[ date ]</a> + <a href="thread.html#10440">[ thread ]</a> + <a href="subject.html#10440">[ subject ]</a> + <a href="author.html#10440">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Dec 14, 2011 at 19:19, Dan Fandrich <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dan at coneharvesters.com</A>> wrote: +><i> On Wed, Dec 14, 2011 at 11:30:33AM +0000, Pascal Terjan wrote: +</I>>><i> On Wed, Dec 14, 2011 at 09:14, Dan Fandrich <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dan at coneharvesters.com</A>> wrote: +</I>>><i> > I can understand that my particular case is unsupported, but I described +</I>>><i> > a different, supported, scenario that would also fail due to this problem. +</I>>><i> > To reiterate, a distribution upgrade from 1 to 2 (once it's finalized) +</I>>><i> > could involve urpmi first upgrading the perl-dependent package but avoid +</I>>><i> > installing the new perl itself until the end of the upgrade, which could be +</I>>><i> > hours or (if interrupted) days later. +</I>>><i> +</I>>><i> During an upgrade urpmi starts by updating what it uses (perl, rpm, +</I>>><i> few other things, itself) and then restarts. +</I>><i> +</I>><i> That has nothing to do with the problem in general. This same issue could +</I>><i> occur with any package that relies on a newer library (even just a newer +</I>><i> point version) but without mentioning that newer library version as a +</I>><i> versioned require. That's the more general issue of which my perl-using +</I>><i> example was but one example. +</I>><i> +</I>>><i> > During the entirety of that time, +</I>>><i> > that package would be unusable. If that package happened to be a key CGI +</I>>><i> > script for a web site, the entire site would be down for that entire time. +</I>>><i> +</I>>><i> That would not be prevented. The result would be that you need to +</I>>><i> install thousands of packages in the same transaction as they are all +</I>>><i> required by each other, and nothing would prevent your CGI from being +</I>>><i> at the end of the transaction which will happen hours or days later. +</I>><i> +</I>><i> All packages are not required by each other. On my system, 13% of packages +</I>><i> are leaves that nothing depends on. 15% depend on nothing other than +</I>><i> glibc, libstdc++ or bash. Another 14% have a single other dependency, in +</I>><i> most cases a tightly-coupled library built from the same source code. So +</I>><i> trying to argue that a transaction must install thousands of packages is +</I>><i> specious.  And RPM's installation sequence is designed to minimize the +</I>><i> window when software is unusable during an upgrade. +</I> +13% of packages may be leaves that nothing depends on, but they will +depend on something and need to be updated at the same time that what +they depend on, so this is not relevant. + +Then you list 29% not depending on much other things, meaning 71% have +more dependencies. +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010429.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI>Next message: <A HREF="010419.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10440">[ date ]</a> + <a href="thread.html#10440">[ thread ]</a> + <a href="subject.html#10440">[ subject ]</a> + <a href="author.html#10440">[ 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> |