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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Changing default media names
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Changing%20default%20media%20names&In-Reply-To=%3C20111120213606.GD21938%40mars-attacks.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009658.html">
<LINK REL="Next" HREF="009660.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Changing default media names</H1>
<B>nicolas vigier</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Changing%20default%20media%20names&In-Reply-To=%3C20111120213606.GD21938%40mars-attacks.org%3E"
TITLE="[Mageia-dev] Changing default media names">boklm at mars-attacks.org
</A><BR>
<I>Sun Nov 20 22:36:06 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009658.html">[Mageia-dev] Changing default media names
</A></li>
<LI>Next message: <A HREF="009660.html">[Mageia-dev] Changing default media names
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9659">[ date ]</a>
<a href="thread.html#9659">[ thread ]</a>
<a href="subject.html#9659">[ subject ]</a>
<a href="author.html#9659">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sun, 20 Nov 2011, Samuel Verschelde wrote:
><i>
</I>><i> I'm not sure about it. I see the benefits, but to me there is a major drawback:
</I>><i> they are not user-friendly :
</I>><i> - current names are readable, new ones aren't, they're just technical
</I>
Adding capitals and replacing / with spaces does not make the name more
user-friendly. If we want to be friendly with users, we should not
confuse them by calling the same thing with different names all the time.
The naming scheme for medias that is used almost everywhere including
on mirrors is i586/core/release, not Core 32bit Release.
><i> - current naming scheme doesn't bother you with arch information, except on 64
</I>><i> bits system and only for 32 bits media
</I>
That's the problem. Sometimes the arch is included, sometimes it is not.
And sometimes two names can refer to different things (Core Release is
not the same thing on x86_64 and i586 installs), or two different names
can refer to the same thing (Core Release on i586 is the same as Core
32bit Release on x86_64 installs).
And 32bit is not more user-friendly than i586. Sources is not more
user-friendly than SRPMS. We should call the same thing with the same
name all the time.
><i> - the order of items in current scheme is better : first you see whether it's
</I>><i> Core, Nonfree or Tainted, then if it's Release/Updates/Backports/Updates
</I>><i> Testing/Backports Testing, and then debug media have some more information.
</I>
The order of items in current scheme is totally random :
Core Release
Core 32bit Release
Core Release Sources
Core Release Debug
Sometimes the arch is not included, sometimes the arch is included as
2nd word (32bit), sometimes the arch is the last word (Sources). Debug
is last, while on mirrors it is not.
If we want to be user-friendly, we should use the same names all the
time, so use the same order all the time.
><i> Release and arch are important but many media share the same release and arch
</I>><i> on a given system, so the information should be more discreet.
</I>
Release and arch in the name is needed to avoid having different medias
with the same name.
><i>
</I>><i> This proposal looks good for CLI but not for GUI. I share the objectives, but
</I>><i> am not entirely convinced by the current proposal, unless it comes with
</I>><i> improvements on the UI side.
</I>><i>
</I>><i> Some ideas :
</I>><i> - change the naming scheme but translate it into human readable names in UI
</I>
I think we should not confuse people by displaying a different name for
the same thing. We can add a description text explaining what the media
is, but this should not be the name.
><i> - Implement item 40 for mageia 2 specs : "really use media tags in the package
</I>><i> managers, CLI and GUI: testing, backport, update, etc. Currently, apart from a
</I>
Using media tags does not replace using consistent media names.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009658.html">[Mageia-dev] Changing default media names
</A></li>
<LI>Next message: <A HREF="009660.html">[Mageia-dev] Changing default media names
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9659">[ date ]</a>
<a href="thread.html#9659">[ thread ]</a>
<a href="subject.html#9659">[ subject ]</a>
<a href="author.html#9659">[ 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>
|
