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
|
<!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=%3C201111202159.19791.alien%40rmail.be%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009657.html">
<LINK REL="Next" HREF="009659.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Changing default media names</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Changing%20default%20media%20names&In-Reply-To=%3C201111202159.19791.alien%40rmail.be%3E"
TITLE="[Mageia-dev] Changing default media names">alien at rmail.be
</A><BR>
<I>Sun Nov 20 21:59:19 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009657.html">[Mageia-dev] Changing default media names
</A></li>
<LI>Next message: <A HREF="009659.html">[Mageia-dev] Changing default media names
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9658">[ date ]</a>
<a href="thread.html#9658">[ thread ]</a>
<a href="subject.html#9658">[ subject ]</a>
<a href="author.html#9658">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op zondag 20 november 2011 21:18:01 schreef Samuel Verschelde:
[...]
><i> Some ideas :
</I>><i> - change the naming scheme but translate it into human readable names in UI
</I>><i> - Implement item 40 for mageia 2 specs : "really use media tags in the
</I>><i> package managers, CLI and GUI: testing, backport, update, etc. Currently,
</I>><i> apart from a hack for media which name contain “backport”, the nature of
</I>><i> the media is not used in urpmi and rpmdrake whereas it could be used to
</I>><i> improve usability a lot. Instead of talking about core-updates,
</I>><i> core-updates_testing, etc., talk about the root media (“core”, “non-free”,
</I>><i> “tainted”) and let users choose whether they want to use updates,
</I>><i> backports, updates_testing,
</I>><i> backports_testing flavors of this root media." I haven't had the time to
</I>><i> write a complete spec for that, but if needed I could try to put it higher
</I>><i> on my TODO list.
</I>><i>
</I>><i> Best regards
</I>><i>
</I>><i> Samuel Verschelde
</I>
i agree.
Also, one problem i see is that naming them like the paths, will give strange
errors if you have more than one repos like that.
One idea could be: have --*media tags also match the local paths:
- cauldron/x86_64/core/release
- ...
also tab completion doesn't work well with all the spaces, definately not if
you want to specify more repos...
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009657.html">[Mageia-dev] Changing default media names
</A></li>
<LI>Next message: <A HREF="009659.html">[Mageia-dev] Changing default media names
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9658">[ date ]</a>
<a href="thread.html#9658">[ thread ]</a>
<a href="subject.html#9658">[ subject ]</a>
<a href="author.html#9658">[ 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>
|
