From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20101008/001043.html | 85 +++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101008/001043.html (limited to 'zarb-ml/mageia-dev/20101008/001043.html') diff --git a/zarb-ml/mageia-dev/20101008/001043.html b/zarb-ml/mageia-dev/20101008/001043.html new file mode 100644 index 000000000..8fdac08a5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001043.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] Proposal: Updating released versions (long post) + + + + + + + + + +

[Mageia-dev] Proposal: Updating released versions (long post)

+ Marc Paré + marc at marcpare.com +
+ Fri Oct 8 22:10:40 CEST 2010 +

+
+ +
+>
+> Wherever this can be done, it usually is.  Multiple versions of
+> libraries can coexist in Linux, so if the new version requires new
+> libraries, there's no conflict.
+>
+> The dependencies that cause problems are, for example,  the situation
+> where you can only have one of a certain service provider and its users
+> are bound to it by an API which changes between the release version and
+> the new version you want to install.  For example, if A, B, C, D, E all
+> use F, and the new version of C has been changed to use the
+> (incompatible) API of the new version of F, you'd have to install all 6.
+>
+>
+>
+
+So, in terms of space used for this, if you had to install all 6, would 
+this tax the system so much and risk filling up the hardrive needlessly.
+
+If not, would this cause your installation to misbehave.
+
+It not, if a rollback were done, could all 6 as well as the new F be 
+removed and the old version restored?
+
+If this is possible, would this have an impact on devs preparing 
+Backport versions with rollbacks?
+
+Marc
+
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1