diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010414.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010414.html | 141 |
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010414.html b/zarb-ml/mageia-dev/2011-December/010414.html new file mode 100644 index 000000000..81db36a6a --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010414.html @@ -0,0 +1,141 @@ +<!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=%3C20111214091458.GA22114%40coneharvesters.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010410.html"> + <LINK REL="Next" HREF="010415.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How broken are RPM dependencies allowed to be?</H1> + <B>Dan Fandrich</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=%3C20111214091458.GA22114%40coneharvesters.com%3E" + TITLE="[Mageia-dev] How broken are RPM dependencies allowed to be?">dan at coneharvesters.com + </A><BR> + <I>Wed Dec 14 10:14:59 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010410.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI>Next message: <A HREF="010415.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10414">[ date ]</a> + <a href="thread.html#10414">[ thread ]</a> + <a href="subject.html#10414">[ subject ]</a> + <a href="author.html#10414">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Dec 14, 2011 at 09:49:15AM +0200, Buchan Milne wrote: +><i> This is unsupported. Maybe you should instead contribute documentation that +</I>><i> makes this more explicitly obvious, but it is a well-known rule in Mandriva and +</I>><i> Mageia (and usually applies to other distros as well). +</I> +I can understand that my particular case is unsupported, but I described +a different, supported, scenario that would also fail due to this problem. +To reiterate, a distribution upgrade from 1 to 2 (once it's finalized) +could involve urpmi first upgrading the perl-dependent package but avoid +installing the new perl itself until the end of the upgrade, which could be +hours or (if interrupted) days later. During the entirety of that time, +that package would be unusable. If that package happened to be a key CGI +script for a web site, the entire site would be down for that entire time. + +><i> If this weren't the case, there wouldn't be a need for backports ... +</I> +Backports are nice in that they are leaf packages that don't generally +require a ton of newer libraries be installed as well. Installing a +single package of any complexity from a newer distribution often results +in a cascading series of new packages to resolve all the dependencies. +But it's often expeditious to upgrade simpler packages in that way in +cases when the system can't completely upgraded right away. + +It's possible to handle that kind of case reliably, but I understand that +it would be more work to get the dependencies just right. Many library +authors put plenty of effort into maintaining binary compatibility across +releases just so this sort of thing is possible. But even if this isn't an +officially-supported mode of operation, problems like the one I described +above can still result in broken systems if the dependencies aren't +correctly described. + +><i> Installing packages individually from one release on another release is not +</I>><i> supported. Either upgrade the entire distro first, or stick to packages from +</I>><i> the version you are on. However 'upgrade from release to Cauldron', when done +</I>><i> correctly, should usually work as expected. +</I> +Yes, "usually". Is Mageia the operating system that works reliably 95% of the +time? + +><i> But, in supported use cases, urpmi *does* ensure that all the pieces to keep +</I>><i> urpmi are upgraded in one transaction. +</I> +But only if the dependencies are set correctly. And my original bug report on +that has just now been closed as WONTFIX. + +><i> Supporting the use case of installing any random package from a different +</I>><i> release will take more effort than just adding and maintaining a version on one +</I>><i> perl-base dependency. +</I> +Yes, it will, but it can be automated to a certain extent. There just has to be +a will to make sure that even the corner cases work. + +>>><i> Dan +</I></PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010410.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI>Next message: <A HREF="010415.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10414">[ date ]</a> + <a href="thread.html#10414">[ thread ]</a> + <a href="subject.html#10414">[ subject ]</a> + <a href="author.html#10414">[ 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> |