| 1 |
On Wed, Jun 15, 2016 at 9:11 PM, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> I would personally go for the following layout: |
| 3 |
> |
| 4 |
> - All packages, |
| 5 |
> - Core system [includes baselayout], |
| 6 |
> - Eclasses and Profiles, |
| 7 |
> - GCC Porting, |
| 8 |
> - Hardened, |
| 9 |
> - Keywording & Stabilization, |
| 10 |
> - New packages ('New ebuilds' previously), |
| 11 |
> - SELinux. |
| 12 |
> |
| 13 |
[...] |
| 14 |
> |
| 15 |
> Your thoughts? |
| 16 |
> |
| 17 |
|
| 18 |
I'd split "eclasses" from "profiles", as they're not normally related |
| 19 |
to each other. |
| 20 |
|
| 21 |
We could also have separate components for "keywording" vs |
| 22 |
"stabilization", which would make the use of STABLEREQ/KEYWORDREQ |
| 23 |
keywords obsolete at the same time. |
| 24 |
|
| 25 |
Thanks, |
| 26 |
Davide |
Archives