diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101008/001042.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101008/001042.html | 97 |
1 files changed, 97 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101008/001042.html b/zarb-ml/mageia-dev/20101008/001042.html new file mode 100644 index 000000000..9cc349e18 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001042.html @@ -0,0 +1,97 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF77F5.3070309%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001038.html"> + <LINK REL="Next" HREF="001043.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF77F5.3070309%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 21:58:45 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1042">[ date ]</a> + <a href="thread.html#1042">[ thread ]</a> + <a href="subject.html#1042">[ subject ]</a> + <a href="author.html#1042">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> So, as to your proposal, I am in agreement with it. Maybe a suggestion +</I>><i> (more of a question), seeing as the issues have to deal more with the +</I>><i> dependencies of a "roll-back", what if, "Backports" would install, +</I>><i> somehow the software updates in a self compartment kind of way (sorry +</I>><i> my language terms may not be descriptive enough). +</I> +Michael hinted at that, either taking a copy-on-write (brtfs) copy of +the user's system for later restore, or having users install the update +on a VM copy of their system, but the image thing is good for only one +update at a time, and I don't think most users are going to re-install +in a VM to test a new package. There really isn't a good way to install +in a "sandbox". + +><i> +</I>><i> Users know that repositories are activated and some are not at the +</I>><i> time of install. I think that most users have a faint idea of this. +</I>><i> But if Backports were to be used more at the user level, what is +</I>><i> clear, is that, there should be a roll-back feature. If the roll-back +</I>><i> feature, as a normal course of rolling-back will or could remove other +</I>><i> softs due to dependencies, then maybe possible option would be to have +</I>><i> the "Backport" software installations install all dependencies in such +</I>><i> a way as to isolate them from the larger distro packages. This would +</I>><i> in effect could make a secondary related-dependency file on the +</I>><i> system. Then if a roll-back were done a Backported software package +</I>><i> only the associated dependencies would be deleted. +</I>><i> +</I>><i> Could this be done? +</I> +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. + + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1042">[ date ]</a> + <a href="thread.html#1042">[ thread ]</a> + <a href="subject.html#1042">[ subject ]</a> + <a href="author.html#1042">[ 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> |