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
|
<!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=%3C20111120224826.GE21938%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="009660.html">
<LINK REL="Next" HREF="009663.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=%3C20111120224826.GE21938%40mars-attacks.org%3E"
TITLE="[Mageia-dev] Changing default media names">boklm at mars-attacks.org
</A><BR>
<I>Sun Nov 20 23:48:26 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009660.html">[Mageia-dev] Changing default media names
</A></li>
<LI>Next message: <A HREF="009663.html">[Mageia-dev] Changing default media names
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9661">[ date ]</a>
<a href="thread.html#9661">[ thread ]</a>
<a href="subject.html#9661">[ subject ]</a>
<a href="author.html#9661">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sun, 20 Nov 2011, Maarten Vanraes wrote:
><i> Op zondag 20 november 2011 22:36:06 schreef nicolas vigier:
</I>><i> > On Sun, 20 Nov 2011, Samuel Verschelde wrote:
</I>><i> > > I'm not sure about it. I see the benefits, but to me there is a major
</I>><i> > > drawback: they are not user-friendly :
</I>><i> > > - current names are readable, new ones aren't, they're just technical
</I>><i> >
</I>><i> > Adding capitals and replacing / with spaces does not make the name more
</I>><i> > user-friendly. If we want to be friendly with users, we should not
</I>><i> > confuse them by calling the same thing with different names all the time.
</I>><i> > The naming scheme for medias that is used almost everywhere including
</I>><i> > on mirrors is i586/core/release, not Core 32bit Release.
</I>><i> >
</I>><i> > > - current naming scheme doesn't bother you with arch information, except
</I>><i> > > on 64 bits system and only for 32 bits media
</I>><i> >
</I>><i> > That's the problem. Sometimes the arch is included, sometimes it is not.
</I>><i> > And sometimes two names can refer to different things (Core Release is
</I>><i> > not the same thing on x86_64 and i586 installs), or two different names
</I>><i> > can refer to the same thing (Core Release on i586 is the same as Core
</I>><i> > 32bit Release on x86_64 installs).
</I>><i> >
</I>><i> > And 32bit is not more user-friendly than i586. Sources is not more
</I>><i> > user-friendly than SRPMS. We should call the same thing with the same
</I>><i> > name all the time.
</I>><i> [...]
</I>><i>
</I>><i> I disagree with you here, I'm all for consistent media names that are easy to
</I>><i> complete, but "Core Release Source" is more userfriendly than
</I>><i> "SRPMS/core/release" . i'm pretty sure my dad would get even more lost than he
</I>><i> is right now.
</I>
For someone who doesn't know anything about our media policy, both names
are equaly meaningless. If we want them to understand something, what is
needed is a description text of the medias.
><i>
</I>><i> imho "Cauldron Core Release (source)" is more userfriendly than
</I>><i> "cauldron/SRPM/core/release". at least to people who don't even know what a
</I>><i> path is.
</I>><i>
</I>><i> it's acceptable for me to:
</I>><i> - no caps
</I>><i> - better ordering
</I>><i> - consistent arch adding
</I>><i>
</I>><i> but using pathnames, albeit the best consistency, is not good.
</I>
Why ?
><i>
</I>><i> imho we should be able in cli to use a unique identifier, but it doesn't have
</I>><i> to be the name as seen.
</I>><i>
</I>><i> if we can use urpm* commands with the path name as identifier, that's ok for me
</I>><i> too.
</I>
Having multiple unique identifiers for each media is not what I would
call user-friendly. We already have the name as unique identifier, there
is no need to add an other one.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009660.html">[Mageia-dev] Changing default media names
</A></li>
<LI>Next message: <A HREF="009663.html">[Mageia-dev] Changing default media names
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9661">[ date ]</a>
<a href="thread.html#9661">[ thread ]</a>
<a href="subject.html#9661">[ subject ]</a>
<a href="author.html#9661">[ 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>
|
