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
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] mageiaupdate and the list of updates
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20mageiaupdate%20and%20the%20list%20of%20updates&In-Reply-To=%3C4E0FAC75.20005%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Next" HREF="004891.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] mageiaupdate and the list of updates</H1>
<B>andre999</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20mageiaupdate%20and%20the%20list%20of%20updates&In-Reply-To=%3C4E0FAC75.20005%40laposte.net%3E"
TITLE="[Mageia-discuss] mageiaupdate and the list of updates">andr55 at laposte.net
</A><BR>
<I>Sun Jul 3 01:40:37 CEST 2011</I>
<P><UL>
<LI>Next message: <A HREF="004891.html">[Mageia-discuss] Contribute web page
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4890">[ date ]</a>
<a href="thread.html#4890">[ thread ]</a>
<a href="subject.html#4890">[ subject ]</a>
<a href="author.html#4890">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Anne nicolas a écrit :
><i> 2011/7/2 Romain d'Alverny<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">rdalverny at gmail.com</A>>:
</I>>><i> Le 2 juil. 2011 à 17:14, andre999<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">andr55 at laposte.net</A>> a écrit :
</I>>>><i> Suppose during the update process you have a check box to put a particular update on
</I>>>><i> the skip list, or another to uninstall the corresponding package.
</I>>><i>
</I>>><i> That would be an interesting option to investigate.
</I>>><i>
</I>>>><i> Note that if you can't uninstall a package because it is required, it is usually
</I>>>><i> inadvisable skip updates, unless you really understand the issues.
</I>>><i>
</I>>><i> So the user is stuck: unadvisable to skip the updates, unless she understands the issues
</I>>><i> => just make the update automatic in a background task by default then; one doesn't care
</I>>><i> about the issues - or won't have a single clue about it either, unless being a specific
</I>>><i> type of user that would know how to disable this auto update setting anyway).
</I>>><i>
</I>>>><i> Changing when the password is requested would reduce the security for the system, as
</I>>>><i> unauthorised users could see what is installed.
</I>>><i>
</I>>><i> Unauthorised users using an authorised session, to be more specific.
</I>
Such a situation is far from rare in multi-user environments.
But also if someone doesn't know the root password, currently they can't see
what is installed. By delaying it until something is actually updated, they can
see everything. So a remote user with limited privileges could more easily
compromise the system.
>><i> Security is important. But that's orthogonal to a pleasant/efficient experience.
</I>>><i> Which is important too. We are aiming at making things for people.
</I>>><i>
</I>>>><i> This may not affect you personnally, but such an option would best not be the
</I>>>><i> default, to protect other systems. So it could be more complicated than the
</I>>>><i> changes suggested above, and would only save you a few seconds.
</I>>><i>
</I>>><i> "a few seconds" is already a lot for everyone (and even more if the notification
</I>>><i> breaks your focus). Multiply this by the times such a notification occurs for a
</I>>><i> typical desktop system, you have a lot of valuable time wasted here.
</I>>><i>
</I>>><i> That's not such a ludicrous idea; improving the person experience with the system
</I>>><i> so she can focus on her task and not on the tool is clearly one of our goals.
</I>><i>
</I>>><i> But indeed, perhaps it only requires making this more obvious (that is, integrated
</I>>><i> in the user flow and interface), how to use the existing options.
</I>><i>
</I>><i> Imho those 2 things are bad ideas:
</I>><i>
</I>><i> - having updates in background: Interesting thing in Linux is to learn
</I>><i> people about their system. If they do not want details, then fine we
</I>><i> can just a way to switch from general mode to detailed one.
</I>
That's one thing I like about Linux. Being able to readily monitor updates in
detail.
><i> - giving the possibility of adding easily packages to skip.list is the
</I>><i> best way to break updates of end users systems. They will skip some
</I>><i> updates when it's too long for example, without really being aware of
</I>><i> what they do.
</I>
That was part of my concerns.
><i> Then if an incoming update depends on a specific version
</I>><i> of skipped package it will just break. I would rather add this as an
</I>><i> advanced option in rpmdrake
</I>
I agree.
Maybe an advanced mode, like in diskdrake. (which I use judiciously)
>><i>
</I>>><i> Romain
</I>
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Next message: <A HREF="004891.html">[Mageia-discuss] Contribute web page
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4890">[ date ]</a>
<a href="thread.html#4890">[ thread ]</a>
<a href="subject.html#4890">[ subject ]</a>
<a href="author.html#4890">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
