1 |
> > [..] |
2 |
> > Most KDE team members didn't want to me touch kde-meta any further, as |
3 |
> > developer modules shouldn't be there because kde-meta is for general user |
4 |
> > consumption, I propose the following: |
5 |
> > remove kdewebdev from kde-meta |
6 |
> > add developer or sdk flag in kde-meta, which will include kdebindings, kdesdk |
7 |
> > and kdewebdev modules. |
8 |
> > Another option is to have another meta package (something like kdefull-meta), |
9 |
> > which I hated. |
10 |
> > Your feedback is welcome. |
11 |
|
12 |
> I use kde-meta and admit I wouldn't want the developer stuff installed |
13 |
> since I am not a dev. Maybe have a kdedev-meta. Then a developer could |
14 |
> install both kde-meta and kdedev-meta, or just kdedev-meta, to get the |
15 |
> developer stuff. |
16 |
> |
17 |
> Basically, if I am a developer I would emerge kdedev-meta to get the |
18 |
> whole shabang. Maybe set kdedev-meta to pull in kde-meta as well. I |
19 |
> would think that with dev in the name, most people would know that is |
20 |
> not a user area as well. kdefull-meta could mislead someone. |
21 |
|
22 |
I am a developer, and I like the idea of 'sdk' use flag. |
23 |
|
24 |
It hit me once, that after emerging kde-meta I was missing some packages. |
25 |
I was expecting that kde-meta would fetch me all the kde programs. |
26 |
|
27 |
Now I know the description says "KDE - merge this to pull in all |
28 |
non-developer packages", but it would be _so_ _easier_ to |
29 |
make kde-meta pull kdesdk-meta, when the 'sdk' use flag is set. |