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-dev] RPM features/issues/wishlist
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RPM%20features/issues/wishlist&In-Reply-To=%3CCAPn0va7ea%3Dtc2wCo2fQM%2Bxv32u7mxCgw9qT%3D8M3WRYSm%2Btb90Q%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="008873.html">
<LINK REL="Next" HREF="008905.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] RPM features/issues/wishlist</H1>
<B>Donald Stewart</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RPM%20features/issues/wishlist&In-Reply-To=%3CCAPn0va7ea%3Dtc2wCo2fQM%2Bxv32u7mxCgw9qT%3D8M3WRYSm%2Btb90Q%40mail.gmail.com%3E"
TITLE="[Mageia-dev] RPM features/issues/wishlist">watersnowrock at gmail.com
</A><BR>
<I>Sat Oct 15 12:22:50 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="008873.html">[Mageia-dev] RPM features/issues/wishlist
</A></li>
<LI>Next message: <A HREF="008905.html">[Mageia-dev] RPM features/issues/wishlist
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8875">[ date ]</a>
<a href="thread.html#8875">[ thread ]</a>
<a href="subject.html#8875">[ subject ]</a>
<a href="author.html#8875">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 14 October 2011 22:04, Liam R E Quin <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">liam at holoweb.net</A>> wrote:
><i>
</I>>><i> The thing about packagekit, well most graphical frontends package
</I>>><i> management (pm) is that they dont really need to be that functional.
</I>>><i> By that I mean that yes it is great to be able to query nearly all of
</I>>><i> urpmi's features in rpmdrake, however, isn't it much faster to just do
</I>>><i> urpmf --files file-name.
</I>><i>
</I>><i>
</I>><i> The people most likely to use a graphical program like rpmdrake are
</I>><i> probably not so comfortable typing cryptic and distribution-specific
</I>><i> shell commands!
</I>><i>
</I>>><i>  I guess what I am getting at is that as long
</I>>><i> as basic functionality, eg searching, add/remove and repo
</I>>><i> configurations are handled by the pm and done properly, ie not causing
</I>>><i> any breakage, then I feel that it is fair enough to say that more
</I>>><i> advanced functions should be done on the cl, firstly because that way
</I>>><i> is easier, secondly because that way encourages less breakage from
</I>>><i> just point and click and see.
</I>><i>
</I>><i> The right answer is that point-and-click-and-see should not break
</I>><i> things.
</I>><i>
</I>><i> Years ago I used to recommend Mandrake Linux when I spoke at
</I>><i> conferences, and one reason was that the admin tools had a log that
</I>><i> showed you what commands were being run, and, if you ran the commands
</I>><i> yourself, the same thing would happen. So it was a way for people to
</I>><i> learn.
</I>><i>
</I>><i> Liam
</I>><i>
</I>><i> --
</I>><i> Liam Quin - XML Activity Lead, W3C, <A HREF="http://www.w3.org/People/Quin/">http://www.w3.org/People/Quin/</A>
</I>><i> Pictures from old books: <A HREF="http://fromoldbooks.org/">http://fromoldbooks.org/</A>
</I>><i>
</I>><i>
</I>
That is what I am saying. A frontend should cover every feature that
is required and can be done sensibly from a gui - without the risk of
allowing a system to break. I don't care how perfect a gui is, it will
always increase the risk of something breaking, I am not saying that
we should remove the option for users to configure things from the
gui, but before we go and implement advanced features - like the
orphan feature - we need to make sure that they work properly, both as
tools and in there communincation, unlike the orphan feature, it did
break many systems.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="008873.html">[Mageia-dev] RPM features/issues/wishlist
</A></li>
<LI>Next message: <A HREF="008905.html">[Mageia-dev] RPM features/issues/wishlist
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8875">[ date ]</a>
<a href="thread.html#8875">[ thread ]</a>
<a href="subject.html#8875">[ subject ]</a>
<a href="author.html#8875">[ 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>
|
