1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
<!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=%3C4CB62FD2.2090303%40roadrunner.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Next" HREF="001171.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=%3C4CB62FD2.2090303%40roadrunner.com%3E"
TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com
</A><BR>
<I>Thu Oct 14 00:16:50 CEST 2010</I>
<P><UL>
<LI>Next message: <A HREF="001171.html">[Mageia-dev] Proposal: Updating released versions (long post)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1161">[ date ]</a>
<a href="thread.html#1161">[ thread ]</a>
<a href="subject.html#1161">[ subject ]</a>
<a href="author.html#1161">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Renaud MICHEL wrote:
><i> On Wednesday 13 octobre 2010 at 23:34, Frank Griffin wrote :
</I>><i>
</I>>><i> One way of doing it might be, having identified packages that require
</I>>><i> this sort of support, to wrap the executables with scripts that do this
</I>>><i> the next time a user runs the software before the real executable is
</I>>><i> launched.
</I>>><i>
</I>><i> Now that's getting very hackish.
</I>><i> I'd rather not have many programs wrapped in scripts that would do some
</I>><i> magic on my home dir under the hood. Because with such a "solution" the
</I>><i> programs would be always wrapped, even if you never do a rollback.
</I>><i> How would such script detect that it actually was a rollback and it should
</I>><i> do his magic on the config files.
</I>><i>
</I>
The wrapper script would be specific to the package version which
provided it. If it finds a saved config file with a name matching its
own version, it restores it and deletes the saved one. If it doesn't,
it does nothing.
><i> What would happen if the user did not run that program between the update
</I>><i> and the rollback?
</I>><i>
</I>
Nothing, because the new wrapper script would never have been executed
to save a previous version, so the restored old wrapper script would not
find anything to restore.
><i> It seems the complexity is not worth the benefit, and those scripts are
</I>><i> likely to not be well tested and might make things worse if things are not
</I>><i> like they expected.
</I>><i>
</I>
That's a pretty broad statement, especially considering the complexity
of some of the wrapper scripts we already have. This is not that
complex, and the benefit of finding a solution is considerable, based on
the previous posts/relies in this thread.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Next message: <A HREF="001171.html">[Mageia-dev] Proposal: Updating released versions (long post)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1161">[ date ]</a>
<a href="thread.html#1161">[ thread ]</a>
<a href="subject.html#1161">[ subject ]</a>
<a href="author.html#1161">[ 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>
|
