blob: 5db61564f20451d2b4464aa59d4b6af8858c49bc (
plain)
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20task-obsolete%20and%20README.%2A.urpmi%20enhancement&In-Reply-To=%3C4F04A938.1060005%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010985.html">
<LINK REL="Next" HREF="010960.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement</H1>
<B>Anssi Hannula</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20task-obsolete%20and%20README.%2A.urpmi%20enhancement&In-Reply-To=%3C4F04A938.1060005%40mageia.org%3E"
TITLE="[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement">anssi at mageia.org
</A><BR>
<I>Wed Jan 4 20:32:08 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="010985.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement
</A></li>
<LI>Next message: <A HREF="010960.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10961">[ date ]</a>
<a href="thread.html#10961">[ thread ]</a>
<a href="subject.html#10961">[ subject ]</a>
<a href="author.html#10961">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 04.01.2012 18:20, Guillaume Rousse wrote:
><i> Here are a few proposal of mines to make the situation better:
</I>><i> - use a unique file name, enforced by convention, rather than references
</I>><i> in package description, the same way Debian does with README.debian
</I>><i> - display its content only in graphical context: command-line users
</I>><i> usually know about this kind of convention to get information themselves
</I>><i> - use standardised file content and markup to allow rpmdrake and other
</I>><i> graphical tools to achieve the same kind of selection than file
</I>><i> splitting today
</I>><i> - define some kind of policy of what should be there, and what should
</I>><i> not, to achieve minimal consistency
</I>
+1
except for the 2nd point; I do want any important information to be
shown automatically. For example, I don't check the documentation of
each and every package on each and every update for upgrade information.
I also agree Johnny, all the information should be shown in the end of
the urpmi run, not in the middle of installing packages where one may
not notice them.
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010985.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement
</A></li>
<LI>Next message: <A HREF="010960.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10961">[ date ]</a>
<a href="thread.html#10961">[ thread ]</a>
<a href="subject.html#10961">[ subject ]</a>
<a href="author.html#10961">[ 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>
|
