1 |
On Fri, 12 Feb 2010 15:46:57 +0100, BRM <bm_witness@×××××.com> wrote: |
2 |
|
3 |
> ----- Original Message ---- |
4 |
> |
5 |
>> From: Zeerak Waseem <zeerak.w@×××××.com> |
6 |
>> On Fri, 12 Feb 2010 10:53:04 +0100, Neil Bothwick wrote: |
7 |
>> > On Fri, 12 Feb 2010 05:19:43 +0100, Zeerak Waseem wrote: |
8 |
>> >> But I do find it silly, that the various applications that aren't |
9 |
>> >> dependent of the DE, to require a dependency of the DE. It just seems |
10 |
>> >> a bit backwards to me :-) I simply don't understand. |
11 |
>> > That just shows that they are still partially dependent on the DE, |
12 |
>> KMail |
13 |
>> > also needs various KDE libraries. KDE was designed as a cohesive DE, |
14 |
>> not |
15 |
>> > just a bunch of applications with a common look and feel. KDE apps are |
16 |
>> > intended to be run on a KDE desktop, anything else is a nice bonus. |
17 |
>> Indeed, and it is a noble pursuit. |
18 |
>> But from a marketing aspect, it would make more sense to have things |
19 |
>> that aren't |
20 |
>> -vital- for the app, unlike kde-libs in this case, to be soft (is this |
21 |
>> the |
22 |
>> correct term?) dependencies. |
23 |
>> Both aspects could be satisfied by having symantic-desktop as an |
24 |
>> optional dep. |
25 |
>> It's not a vital function for kmail to be able to tag and index all the |
26 |
>> files on |
27 |
>> the computer (which is what the symantic-desktop does if I understand |
28 |
>> correctly), it's a nifty thing for KDE users, and soon probably Gnome |
29 |
>> users as |
30 |
>> well, but for anyone else, it's a nifty thing -if- they feel the need |
31 |
>> for it. |
32 |
>> Much like most other bits of software :-) |
33 |
> |
34 |
> Obviously you don't understand the reason for the dependency. |
35 |
> It does not exist so that Kmail can index all the files on the system |
36 |
> but for the opposite - |
37 |
> so that Kmail can participate in the search by allowing the system to be |
38 |
> able to search _its_ data. |
39 |
> |
40 |
> And, btw, you're not turning it off within Kmail, but at the system - DE |
41 |
> - level. |
42 |
> The application itself will still check to see if it could participate, |
43 |
> only to have nothing turned on to support so then it doesn't do anything. |
44 |
> |
45 |
|
46 |
Right, but then when the DE isn't a DE, but a window manager, a minimal |
47 |
one, then it's kind of a strange for a function to be forced outside of |
48 |
the specific DE. Well it seems strange to me anyway. |
49 |
|
50 |
>> In the end there isn't a right or wrong, but just a standpoint. |
51 |
> |
52 |
> Question: are you a software developer? |
53 |
> |
54 |
> Kmail probably has the dependency the way they do b/c it is far easier |
55 |
> to make it one and let the system determine not to support the |
56 |
> functionality |
57 |
> than it is to litter the codebase with "if (symanticDesktopEnabled)..." |
58 |
> code. |
59 |
> |
60 |
|
61 |
An aspiring one, yes. And it probably easier to just make it a hard dep, |
62 |
however if the quality of their application for anyone -not- using kde. |
63 |
It's sensible for it being set if you have kde, but if you don't have kde |
64 |
it just seems very out of place. |
65 |
|
66 |
>> Some don't mind |
67 |
>> the bloat (we can agree that it's bloat if you're just going to disable |
68 |
>> the |
69 |
>> function as soon as it's been installed, right?) and don't consider it |
70 |
>> to be the |
71 |
>> slightest bit akin to bloat, whilst to others it's an unnecessary |
72 |
>> feature forced |
73 |
>> on them (mainly thinking of the people not using kde, but also those |
74 |
>> kde-users |
75 |
>> that just disable it) and thus becomes bloat. |
76 |
> |
77 |
> No more than it is bloat for gcc to support mmx/sse/sse2/sse3/sse4 when |
78 |
> your processor cannot. |
79 |
> |
80 |
> Ben |
81 |
> |
82 |
> |
83 |
> |
84 |
|
85 |
I hadn't considered that particular thing, but yes, in a sense you're |
86 |
right. I mean there is difference for a compiler and a mail app, with gcc |
87 |
you can compile for another system so the it supports things your |
88 |
processor doesn't support doesn't necessarily mean that you won't need the |
89 |
support, with a mail app you can... But essentially, if you know you'll |
90 |
never need to compile for another processor, then yes I'd consider it |
91 |
bloat. |
92 |
|
93 |
-- |
94 |
Zeerak |