| 1 |
Hi, |
| 2 |
|
| 3 |
The following bugs have ebuilds (and eclass) attached that allow darwin |
| 4 |
or macos users to emerge (or remerge in case of macos) the xnu kernel. |
| 5 |
|
| 6 |
58597 |
| 7 |
59976 |
| 8 |
59994 |
| 9 |
58618 |
| 10 |
58608 |
| 11 |
59991 |
| 12 |
|
| 13 |
The idea is to move the kernel into sys-kernel, try and merge the |
| 14 |
eclass with kernel.eclass (as much as possible - this eclass can also |
| 15 |
(optionally) compile the kernel). cc_tools and the bootstrap stuff can |
| 16 |
probably fit some other categories (to be determined - probably |
| 17 |
sys-something). Please review and write bugcomments if needed. |
| 18 |
|
| 19 |
23:28 <keetz> harsh criticisms are very welcome.... |
| 20 |
|
| 21 |
I couldn't have said it any better. The reason for announcing the |
| 22 |
'ready for testing' availability of this darwin, core macos stuff is |
| 23 |
that the drivers to go with xnu will require a new category. Our last |
| 24 |
dev discussion on drivers resulted into the sys-driver category |
| 25 |
proposal. Is everyone ok with that category for kernel drivers? (Maybe |
| 26 |
even drivers for other software too?) I would like to have closure on |
| 27 |
where to put drivers for modular kernels by the end of this week. |
| 28 |
|
| 29 |
Best regards, |
| 30 |
|
| 31 |
Pieter Van den Abeele |
Archives