| 1 |
On Thu, 16 Jun 2016 00:01:52 +0200 |
| 2 |
"Andreas K. Huettel" <dilfridge@g.o> wrote: |
| 3 |
|
| 4 |
> > Right now we have the following components: |
| 5 |
> > |
| 6 |
> > - Applications, |
| 7 |
> merge with unspecified |
| 8 |
|
| 9 |
Merging is impossible. |
| 10 |
|
| 11 |
> > - Core system, |
| 12 |
> autoassign to base-system? |
| 13 |
|
| 14 |
Will base-system handle systemd bugs? I doubt it. It reminds me of |
| 15 |
auto-assignment to games which resulted in many bugs hitting /dev/null. |
| 16 |
|
| 17 |
> > - Development, |
| 18 |
> makes no sense, merge with unspecified |
| 19 |
> |
| 20 |
> > - Eclasses and Profiles, |
| 21 |
> split into eclasses and profiles |
| 22 |
|
| 23 |
Splitting is impossible. I can create two new components, if you |
| 24 |
insist, and disable the old one. |
| 25 |
|
| 26 |
> > - Games, |
| 27 |
> merge with applications |
| 28 |
> |
| 29 |
> > - Java, |
| 30 |
> auto-assign to java |
| 31 |
|
| 32 |
Why is Java special? Just because nobody uses it? |
| 33 |
|
| 34 |
> > - Library, |
| 35 |
> merge with unspecified |
| 36 |
> |
| 37 |
> > - Printing, |
| 38 |
> either autoassign to printing or merge with unspecified |
| 39 |
> |
| 40 |
> > - Server, |
| 41 |
> does anyone actually use this? |
| 42 |
|
| 43 |
Yes. Reasons unclear. |
| 44 |
|
| 45 |
> > - All packages, |
| 46 |
> > - Core system [includes baselayout], |
| 47 |
> > - Eclasses and Profiles, |
| 48 |
> > - GCC Porting, |
| 49 |
> > - Hardened, |
| 50 |
> > - Keywording & Stabilization, |
| 51 |
> > - New packages ('New ebuilds' previously), |
| 52 |
> > - SELinux. |
| 53 |
> > |
| 54 |
> |
| 55 |
> This is pretty close to the result of above reassignment, however,... |
| 56 |
> |
| 57 |
> > Keeping the big pseudo-category split doesn't make much sense as most |
| 58 |
> > of the packages can't be fit easily into a specific group and it only |
| 59 |
> > confuses users. GNOME & KDE aren't very clear either, especially for |
| 60 |
> > non-core packages (like: is systemd a GNOME package?). Having them |
| 61 |
> > skip bug-wranglers doesn't sound really helpful. |
| 62 |
> |
| 63 |
> Keeping the big desktop environments would be nice; anything that is a large, |
| 64 |
> logical group of packages maintained by one team. |
| 65 |
> |
| 66 |
> Like, auto-assigning kde to kde and gnome to gnome. |
| 67 |
> |
| 68 |
> Of course upstream doesn't really help with their destructive tendencies. |
| 69 |
> ("There is no KDE5, only Frameworks, Plasma and Applications.") |
| 70 |
|
| 71 |
But there are non-core KDE apps that are not maintained by KDE team, |
| 72 |
and GNOME apps that are not maintained by GNOME team. Users usually |
| 73 |
don't check maintainers before choosing a component... |
| 74 |
|
| 75 |
-- |
| 76 |
Best regards, |
| 77 |
Michał Górny |
| 78 |
<http://dev.gentoo.org/~mgorny/> |
Archives