1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
2 |
> In February's KDE meeting I raised the issue that kde-meta (and accordingly |
3 |
> @kde-* sets) don't include all KDE modules [1]. kde-meta excludes developer |
4 |
> modules (well, at least it should, for some reason it includes kdewebdev). |
5 |
> Most KDE team members didn't want to me touch kde-meta any further, as |
6 |
> developer modules shouldn't be there because kde-meta is for general user |
7 |
> consumption, I propose the following: |
8 |
> remove kdewebdev from kde-meta |
9 |
> add developer or sdk flag in kde-meta, which will include kdebindings, kdesdk |
10 |
> and kdewebdev modules. |
11 |
> Another option is to have another meta package (something like kdefull-meta), |
12 |
> which I hated. |
13 |
> Your feedback is welcome. |
14 |
> |
15 |
|
16 |
I use kde-meta and admit I wouldn't want the developer stuff installed |
17 |
since I am not a dev. Maybe have a kdedev-meta. Then a developer could |
18 |
install both kde-meta and kdedev-meta, or just kdedev-meta, to get the |
19 |
developer stuff. |
20 |
|
21 |
Basically, if I am a developer I would emerge kdedev-meta to get the |
22 |
whole shabang. Maybe set kdedev-meta to pull in kde-meta as well. I |
23 |
would think that with dev in the name, most people would know that is |
24 |
not a user area as well. kdefull-meta could mislead someone. |
25 |
|
26 |
Just a thought. |
27 |
|
28 |
Dale |
29 |
|
30 |
:-) :-) |