| 1 |
> Right now we have the following components: |
| 2 |
> |
| 3 |
> - Applications, |
| 4 |
merge with unspecified |
| 5 |
|
| 6 |
> - Core system, |
| 7 |
autoassign to base-system? |
| 8 |
|
| 9 |
> - Development, |
| 10 |
makes no sense, merge with unspecified |
| 11 |
|
| 12 |
> - Eclasses and Profiles, |
| 13 |
split into eclasses and profiles |
| 14 |
|
| 15 |
> - Games, |
| 16 |
merge with applications |
| 17 |
|
| 18 |
> - Java, |
| 19 |
auto-assign to java |
| 20 |
|
| 21 |
> - Library, |
| 22 |
merge with unspecified |
| 23 |
|
| 24 |
> - Printing, |
| 25 |
either autoassign to printing or merge with unspecified |
| 26 |
|
| 27 |
> - Server, |
| 28 |
does anyone actually use this? |
| 29 |
|
| 30 |
|
| 31 |
> |
| 32 |
> - All packages, |
| 33 |
> - Core system [includes baselayout], |
| 34 |
> - Eclasses and Profiles, |
| 35 |
> - GCC Porting, |
| 36 |
> - Hardened, |
| 37 |
> - Keywording & Stabilization, |
| 38 |
> - New packages ('New ebuilds' previously), |
| 39 |
> - SELinux. |
| 40 |
> |
| 41 |
|
| 42 |
This is pretty close to the result of above reassignment, however,... |
| 43 |
|
| 44 |
> Keeping the big pseudo-category split doesn't make much sense as most |
| 45 |
> of the packages can't be fit easily into a specific group and it only |
| 46 |
> confuses users. GNOME & KDE aren't very clear either, especially for |
| 47 |
> non-core packages (like: is systemd a GNOME package?). Having them |
| 48 |
> skip bug-wranglers doesn't sound really helpful. |
| 49 |
|
| 50 |
Keeping the big desktop environments would be nice; anything that is a large, |
| 51 |
logical group of packages maintained by one team. |
| 52 |
|
| 53 |
Like, auto-assigning kde to kde and gnome to gnome. |
| 54 |
|
| 55 |
Of course upstream doesn't really help with their destructive tendencies. |
| 56 |
("There is no KDE5, only Frameworks, Plasma and Applications.") |
| 57 |
|
| 58 |
-- |
| 59 |
|
| 60 |
Andreas K. Huettel |
| 61 |
Gentoo Linux developer |
| 62 |
dilfridge@g.o |
| 63 |
http://www.akhuettel.de/ |
Archives