> Right now we have the following components:
>
> - Applications,
merge with unspecified
> - Core system,
autoassign to base-system?
> - Development,
makes no sense, merge with unspecified
> - Eclasses and Profiles,
split into eclasses and profiles
> - Games,
merge with applications
> - Java,
auto-assign to java
> - Library,
merge with unspecified
> - Printing,
either autoassign to printing or merge with unspecified
> - Server,
does anyone actually use this?
>
> - All packages,
> - Core system [includes baselayout],
> - Eclasses and Profiles,
> - GCC Porting,
> - Hardened,
> - Keywording & Stabilization,
> - New packages ('New ebuilds' previously),
> - SELinux.
>
This is pretty close to the result of above reassignment, however,...
> Keeping the big pseudo-category split doesn't make much sense as most
> of the packages can't be fit easily into a specific group and it only
> confuses users. GNOME & KDE aren't very clear either, especially for
> non-core packages (like: is systemd a GNOME package?). Having them
> skip bug-wranglers doesn't sound really helpful.
Keeping the big desktop environments would be nice; anything that is a large,
logical group of packages maintained by one team.
Like, auto-assigning kde to kde and gnome to gnome.
Of course upstream doesn't really help with their destructive tendencies.
("There is no KDE5, only Frameworks, Plasma and Applications.")
--
Andreas K. Huettel
Gentoo Linux developer
[email protected]
http://www.akhuettel.de/
