diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101008/001045.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101008/001045.html | 102 |
1 files changed, 102 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101008/001045.html b/zarb-ml/mageia-dev/20101008/001045.html new file mode 100644 index 000000000..5ecf1388b --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001045.html @@ -0,0 +1,102 @@ +<!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=%3C4CAF7FC3.50805%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001043.html"> + <LINK REL="Next" HREF="001048.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=%3C4CAF7FC3.50805%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 22:32:03 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1045">[ date ]</a> + <a href="thread.html#1045">[ thread ]</a> + <a href="subject.html#1045">[ subject ]</a> + <a href="author.html#1045">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> +</I>><i> So, in terms of space used for this, if you had to install all 6, +</I>><i> would this tax the system so much and risk filling up the hardrive +</I>><i> needlessly. +</I> +Not really, since the old versions would be removed when the new ones +were installed. The behavior I described is not part of the proposal; +that's what happens today. + +><i> +</I>><i> It not, if a rollback were done, could all 6 as well as the new F be +</I>><i> removed and the old version restored? +</I> +Yes, that's exactly what happens today.The problem is that today, +removing them may cause tons of other packages to have to be removed +because they require things that A-F provide. This wasn't a problem on +upgrade, because the removal of the old and the addition of the new was +a single urpmi "transaction" (I put this in quotes because urpmi uses +"transaction" to mean something other than what I mean here), and urpmi +"knew" that the new versions supplied all the things that vanished when +the old versions were removed. Today, rollbacks have to be done +manually - remove new, then install old. Urpmi doesn't know at the time +of the removal that you're going to turn around and install the old +versions next. It only sees that all the things that both the old and +new versions supply are about to disappear from your system, so it tells +you that you have to remove any other package which requires those things. +><i> +</I>><i> If this is possible, would this have an impact on devs preparing +</I>><i> Backport versions with rollbacks? +</I> +RPM dependencies aren't a problem. Urpmi/urpme know all about them. +The only packaging changes would be for situations like that where a new +version of an application has changed a format of one of its files in +your home directory and the new version automatically converts the old +version of the file to the new format. In that case, the package would +need install scriptlets that copied the old version somewhere so that it +could be restored at uninstall time, otherwise the old version of the +software won't be able to use the new file format. + +The biggest chunk of development involved in the proposal is to make +urpmi do a rollback as a single operation, just as it does an upgrade. +This already exists, in a way; there is a facility called urpmi.recover +that does this type of thing. Bit it's not really considered +mainstream, and I don't think it's been supported for a while. + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1045">[ date ]</a> + <a href="thread.html#1045">[ thread ]</a> + <a href="subject.html#1045">[ subject ]</a> + <a href="author.html#1045">[ 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> |