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
|
<br><br><div class="gmail_quote">Στις 11 Απριλίου 2012 3:53 μ.μ., ο χρήστης Wolfgang Bornath <span dir="ltr"><<a href="mailto:molch.b@googlemail.com">molch.b@googlemail.com</a>></span> έγραψε:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/4/11 Olav Vitters <<a href="mailto:olav@vitters.nl">olav@vitters.nl</a>>:<br>
> On Wed, Apr 11, 2012 at 02:23:36PM +0200, Wolfgang Bornath wrote:<br>
>> > Seems you're just repeating what I suggested: if there is a need, check<br>
>> > if it can be possible.<br>
>><br>
>> Hmm, Obviously we are talking about different things. I thought I<br>
>> clearly showed that there is a need and that the topic of thei thread<br>
>> is to find a solution.<br>
><br>
> The thread is just a request to exclude documentation. IMO the real need<br>
> is unclear (not only disk space apparently). If you fulfill every<br>
> request right away, you'll end up with a lot of options. Better to<br>
> analyse why something is asked and provide that. Gives a better<br>
> experience than just another option somewhere.<br>
><br>
>> > At the moment the only concern seems to be disk space. If that is the<br>
>> > only reason, just do it automatically and/or have a special disk space<br>
>> > concious section. Fully analysing why to exclude would allow that will<br>
>> > ensure it is there when expected, instead of just being an option you<br>
>> > have to search for.<br>
>><br>
>> No, disk space is not the only reason but the most prominent. For the<br>
>> rest of this paragraph I have no clue what you are talking about.<br>
>> Either it's the language barrier or maybe my lack of tech<br>
>> understanding.<br>
><br>
> I mean that is is better to know more than "exclude documentation". That<br>
> is just a request, but I don't get why it is made. E.g. if the sole<br>
> reason would be to minimize disk space, then the most logical thing is<br>
> to include this where disk space is handled.<br>
><br>
> I'm not talking technical, but more use cases.<br>
><br>
> E.g. yesterday one of my disks was full. I could easily resolve, but<br>
> once you understand that one of the reasons for the exclusion of<br>
> documentation is disk space, then you can put intelligence to exclude<br>
> documentation not only in the Mageia installer, but also in the<br>
> notification of not enough disk space (you could have an option to<br>
> remove the documentation on disk). Similarly, if I move to a bigger<br>
> disk, I might want to easily reinstall the documentation that was<br>
> manually removed.<br>
><br>
> Now if the only possibility to exclude documentation was in the Mageia<br>
> installer, then such an installer option doesn't really help when you<br>
> lack disk space later on.<br>
><br>
> Hope you're getting what I am after.<br>
><br>
> Btw: I am not trying to do anything near "stop energy", just want to<br>
> understand the use case better. The "why" is what I am after.<br>
<br>
Yes, I see, thx for clarification.<br>
<br>
Now, we have several use cases here:<br>
<br>
1 - disk is small (I have a netbook with a 4Gb SSD), I don't want to<br>
waste space for ballast.<br>
2 - disk is small, I don't want to waste space for ballast but I want<br>
some handbooks and/or some documentation (meaning I can mark the<br>
handbook I want and leave out all others)<br>
3 - disk space is no issue but I do not want to bloat the installation<br>
and only want the software installed which I really use.<br>
4 - disk space is no issue but I want to save download ressources when<br>
doing updates with rpmdrake (where you can't just say '--no-suggests')<br>
5 - disk space becomes an issue later so I want to remove all the<br>
handbooks with rpmdrake but not the applications themselves. And I<br>
don't want to go 'rpm -e -nodeps' for each and every single handbook<br>
<br>
I am sure there are more use cases, for me the need for a small<br>
installation was the small SSD in the netbook but I also think as #3<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
wobo<br>
</font></span></blockquote></div><br>On the other hand if someone has a real limit with hard disk space, he can use another DE as icewm or lxde.<br>Or in KDE he can delete the handbook folder (doc/HTML) and what ever folder thinks that takes usefulness place in the drive. <br>
If we don't provide the handbooks (with the applications) we will devalue its importance, and personally will be very discouraged to translate them.<br><br>* I am not at home, actually how much space they take ? For what kind of size we are talking about ?<br>
<br> <br clear="all"><br>-- <br><div>Dimitrios Glentadakis</div><br>
|
